Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62361 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47512 invoked from network); 21 Aug 2012 21:21:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2012 21:21:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.128 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.128 c2bthomr10.btconnect.com Received: from [213.123.20.128] ([213.123.20.128:14007] helo=mail.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/E7-10139-ABBF3305 for ; Tue, 21 Aug 2012 17:21:00 -0400 Received: from host81-138-11-136.in-addr.btopenworld.com (EHLO _10.0.0.5_) ([81.138.11.136]) by c2bthomr10.btconnect.com with ESMTP id IVS89754; Tue, 21 Aug 2012 22:20:55 +0100 (BST) Message-ID: <5033FBB3.3000201@lsces.co.uk> Date: Tue, 21 Aug 2012 22:20:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10 MIME-Version: 1.0 To: PHP internals References: <5032A163.9040500@toolpark.com> <5032A880.9050500@lsces.co.uk> <5033EFA4.6050501@toolpark.com> In-Reply-To: <5033EFA4.6050501@toolpark.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.5033FBB4.0071, actions=tag X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.8.21.203315:17:7.944, ip=81.138.11.136, rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __HAS_FROM, __USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __CT, __CT_TEXT_PLAIN, __CTE, __ANY_URI, __URI_NO_MAILTO, __URI_NO_WWW, __CP_URI_IN_BODY, BODY_ENDS_IN_URL, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, RDNS_SUSP, BODY_SIZE_7000_LESS X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.5033FBB7.00CB:SCFSTAT14830815,ss=1,re=-4.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] Official Userland Library (was: removing an item from an array) From: lester@lsces.co.uk (Lester Caine) Lars Schultz wrote: > Am 20.08.2012 23:13, schrieb Lester Caine: >> Boilerplates on how to do more complex operations sounds a very good >> idea to me. It's exactly the sort of thing I've been asking for ... > I am glad you like the idea!;) although "boilerplate" does seem to leave a > metallic aftertaste in my mouth. I run some model engineering sites ;) >> especially now that the vast majority of third party tutorials are no >> longer suitable? Rasmus has pointed out the same problem only in the > Are you referring to "Rasmus Schultz" from the "removing an item from an array" > thread? As far as I understood, Rasmus is arguing in favor of having more > functionality built into core, while I am arguing, that a lot of functionality > should go into the documentation first, as a userland implementation. I am not > sure I understand what you're getting at. No Rasmus Lerdorf was sorting out a problem for someone who was 'following a tutorial' which was no longer correct. >> last hour, and while trying to sort my own mysqlnd compile problem, the >> number of totally out of data results from google just re-enforce that >> situation. > You mean that when you're googling you get bad results, because of the > whitespread use of php? I know what you mean. If good and proven examples of > common problems would be within the official documentation, no googling would be > necessary. Exactly ... >> Even PEAR is little use as a good example of coding style since it needs >> to be updated to be strict compliant in a tidy way - rather than just >> fire fighting error messages. > Personally I have never used PEAR, so I can't say anything about the situation > there, but I can imagine that maintaining such a large codebase has it's > disadvantages. This could probably happen to my idea as well...causing lots of > necessary maintenance-work, I mean. But since its userland code, lots of people > can work on the problem. Also the kind of code I'd like to see there is very > concise and bare-bones, so it probably won't need much adjustment to new > php-versions. Just spent the last two days getting a customers joomla sites working again ... first problem ... add error_reporting( E_ALL & ~E_STRICT & ~E_WARNING ); to the config file to hide all the errors and warnings. >> Using them as a replacement for tidying up core functions may be a >> little controversial, but it does seem the ideal idea for archiving the >> excellent examples that have been presented on the various lists? If >> they then form the base for an update to a core function, then the >> boilerplates just get updated to be current. >> > That's something I thought of too. If some functionality becomes very popular > (difficult to measure, I guess) it could go into core, AFTER it's proven its > worth in real-world applications. I'm still having trouble finding out the preferred way to use some of the basics - stuff I've used for years but now throws warnings :( And a clean boilerplate design without some of the esoteric bells and whistles would be nice. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk