Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78645 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57624 invoked from network); 4 Nov 2014 16:20:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Nov 2014 16:20:37 -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.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:42759] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/98-06676-3DCF8545 for ; Tue, 04 Nov 2014 11:20:36 -0500 Received: (qmail 4844 invoked by uid 89); 4 Nov 2014 16:20:32 -0000 Received: by simscan 1.3.1 ppid: 4830, pid: 4840, t: 0.2500s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.163.79.60) by mail4.serversure.net with ESMTPA; 4 Nov 2014 16:20:32 -0000 Message-ID: <5458FCCF.5050509@lsces.co.uk> Date: Tue, 04 Nov 2014 16:20:31 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: PHP internals References: <5458CEAF.7060204@lsces.co.uk> <5458D492.9040207@lsces.co.uk> <5458E306.50006@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Debugging code ... From: lester@lsces.co.uk (Lester Caine) On 04/11/14 14:45, Peter Lind wrote: > I'd suggest an alternative: fork PHP and only merge bugfixes in to your > own version. Best of both worlds, you get to keep your beloved PHP > pristine without any of the cumbersome new features, and the rest of us > can enjoy an evolving language. In hind sight that is perhaps a choice that SHOULD have been made when e_strict was introduced. I still have a lot of code that will not run on a stock PHP5.4 installation but is running live sites quite happily on an older setup and care has to be taken of any security problems found anyway. The evolution I am still awaiting is to be able to use the unicode material I have in the databases directly in PHP arrays rather than having to take care of ordering externally ... and that perhaps is the only reason I didn't freeze ... -- 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