Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95007 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13977 invoked from network); 10 Aug 2016 13:46:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2016 13:46:23 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.230 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.230 mail4-3.serversure.net Linux 2.6 Received: from [217.147.176.230] ([217.147.176.230:35872] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/B1-05841-D203BA75 for ; Wed, 10 Aug 2016 09:46:23 -0400 Received: (qmail 21460 invoked by uid 89); 10 Aug 2016 13:46:18 -0000 Received: by simscan 1.3.1 ppid: 21454, pid: 21457, t: 0.0742s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 10 Aug 2016 13:46:18 -0000 To: internals@lists.php.net References: <9ccdcfcd-7a1c-42df-c893-398781e1f1d2@lsces.co.uk> Message-ID: Date: Wed, 10 Aug 2016 14:46:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Function auto-loading From: lester@lsces.co.uk (Lester Caine) On 10/08/16 12:14, Michał Brzuchalski wrote: > @Peter and @Rowan: Very good point and sounds reasonable, I also thing > there is need for evolution. Idea of fork PHP and never update made me > laugh to tears :) To be quite honest ... I do now wish that I had simply forked PHP5.3 and maintained that with security fixes, although the ISP's who still support that have done a reasonable job. I decided that it was better to pull everybody over to PHP5.4 and so all the older services could be shut down, but it is not a 5 minute job transferring a legacy site and there are still a large number left to resolve. More irritating is that I have a framework that I've moved everything onto so as to loose the the legacy problems altogether, but while it runs perfectly cleanly on PHP7, it is not written in a style that allows things like 'namespace' to be integrated. Some of the libraries ARE being reworked in a manor that 'modernises' them, but most definitely breaks compatibility with existing code. Things like moving from Smarty 2 to Smarty 3 and then loosing the compatibility wrapper took months, but now the new 'loader' for Smarty 3 is clashing with the legacy Smarty based projects and it is that sort of hassle that simply crushes any pleasure in coding these days, when there is nothing gained by this move to 'auto-loading' libraries as the standard for everybody. -- 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