Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95027 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59739 invoked from network); 10 Aug 2016 19:58:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2016 19:58:04 -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:40941] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/05-32735-9478BA75 for ; Wed, 10 Aug 2016 15:58:02 -0400 Received: (qmail 29935 invoked by uid 89); 10 Aug 2016 19:57:58 -0000 Received: by simscan 1.3.1 ppid: 29925, pid: 29930, t: 0.0870s 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 19:57:58 -0000 To: internals@lists.php.net References: <9ccdcfcd-7a1c-42df-c893-398781e1f1d2@lsces.co.uk> Message-ID: Date: Wed, 10 Aug 2016 20:57:58 +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: 7bit Subject: Re: [PHP-DEV] Function auto-loading From: lester@lsces.co.uk (Lester Caine) On 10/08/16 20:36, Peter Lind wrote: >>From what i can tell, Lester has an infrastructure problem. Not a PHP > problem. But he still wants to halt language development so the community > doesn't pick up new features that might make problems in his code. That > does not seem reasonable to me. Yes I do have an infrastructure problem ... I can't see an easy way to switch from a traditional PHP model to one based on composer and PSR rules. Even processing legacy code much of which still uses little things like 'short tags' into a format that runs cleanly on later versions of PHP takes time. The scripts I have do a good job, but almost every site has had several hours bug checking to clear the remaining missed