Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84192 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 643 invoked from network); 2 Mar 2015 22:01:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2015 22:01: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 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:42026] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/6F-14834-59DD4F45 for ; Mon, 02 Mar 2015 17:00:59 -0500 Received: (qmail 16559 invoked by uid 89); 2 Mar 2015 22:00:40 -0000 Received: by simscan 1.3.1 ppid: 16505, pid: 16534, t: 22.5120s 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.189.147.37) by mail4.serversure.net with ESMTPA; 2 Mar 2015 22:00:17 -0000 Message-ID: <54F4DD6B.6090809@lsces.co.uk> Date: Mon, 02 Mar 2015 22:00:11 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <5E7DF0C5-BCB4-432A-A876-A5057FEBFBB5@gmail.com> <54F320E9.5000706@fischer.name> <54F4159A.6010903@fischer.name> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Consistent function names From: lester@lsces.co.uk (Lester Caine) On 02/03/15 21:39, Yasuo Ohgaki wrote: > I wrote almost complete list. Please take a look at > https://wiki.php.net/rfc/consistent_function_names#list_of_functions_to_be_renamed While the idea of this is well meant, this is another major problem for developers working with substantial legacy code yet needing to update third party libraries. The statement "You can use old names for good." is all very well, but if one library has been 'modernised and another not, one has to work with both sets of names in parallel ... or maintain legacy copies of the same libraries. Updating the PHP documentation is all very well, but how about tutorials, books, third party tools and so on. I would still like some help to update PHPEclipse to the recent PHP5 changes without having to code a complete new set of reserved words and highlighting ... ore reason to simply ditch PHP7 ... -- 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