Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71242 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16579 invoked from network); 18 Jan 2014 13:22:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2014 13:22:49 -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.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:35481] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E5/01-08251-7208AD25 for ; Sat, 18 Jan 2014 08:22:48 -0500 Received: (qmail 13677 invoked by uid 89); 18 Jan 2014 13:22:44 -0000 Received: by simscan 1.3.1 ppid: 13668, pid: 13674, t: 0.0656s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 18 Jan 2014 13:22:44 -0000 Message-ID: <52DA80B4.7000707@lsces.co.uk> Date: Sat, 18 Jan 2014 13:25:08 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 5.5 to 5.6 cleanup From: lester@lsces.co.uk (Lester Caine) Arvids Godjuks wrote: >> Also, nobody can miss the deprecation, as nobody jumps over versions > while migrating (e.g, moving directly from 5.4 to 5.6). >> >Julien.P > Well, on a side note, I actually jumped from 5.3 to 5.5 completely ignoring > 5.4:) This is the reality! And the cause of many of the problems. I'm still tied to 5.4 because much of my customer base is still tied to XP/2000 and the move is from PHP5.2 to 5.4. However it would probably have been easier to clean up all the code on 5.3 before then reworking it again for 5.4. The one thing that is still very lacking is a good tutorial on e_strict compliant design. 95% of search results still pull up mysql code and does not provide good examples of 'modern design'. Since many existing users are still reliant on legacy code, it's a good conversion guide which is more important and not something that single version migration guides actually helps with. This is the main reason I'm trying to develop some more complete guides, but I just don't understand why may own perfectly functional code is no longer acceptable much of the time :( It just creates e_strict warnings and errors. -- 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