Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84500 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81443 invoked from network); 10 Mar 2015 09:27:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Mar 2015 09:27:50 -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:36461] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/01-08808-319BEF45 for ; Tue, 10 Mar 2015 04:27:48 -0500 Received: (qmail 31405 invoked by uid 89); 10 Mar 2015 09:27:44 -0000 Received: by simscan 1.3.1 ppid: 31397, pid: 31402, t: 0.0770s 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; 10 Mar 2015 09:27:44 -0000 Message-ID: <54FEB910.5000608@lsces.co.uk> Date: Tue, 10 Mar 2015 09:27:44 +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: <5D8591E2-5AE6-4B4C-AAE0-3D15523410AC@gmail.com> <54F83C4D.1020206@gmail.com> <54F8BF67.6080600@gmail.com> <848D3C19-DE29-4E5F-9B23-D87D3F4A9365@gmail.com> <54FB45D6.3040803@gmail.com> <54FCD063.4040300@gmail.com> 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 10/03/15 01:59, Yasuo Ohgaki wrote: > The same argument applies to fresh new OO APIs. It's just a matter of > targeted PHP version to be supported. There are many things to be > considered to decide targeted PHP version other than this RFC. We have many > new features/behaviors in newer PHP versions. I still have a major problem with the whole basis of your re-naming ... adding the underscore at all. It was this introduction which was totally wrong in the first place and I would rather rename the incorrectly renamed functions if only to make them consistent with what is used in the OO 'standard'. $main->phpVersion() or phpversion() Is consistent if one maintains the case insensitive rule. Adding str_ in front of every string function where a lot are IEEE protected is just adding confusion. Where these map to an OO API in my book strcmp() $str->cmp() makes sense? Adding an extra $str_cmp is simply not necessary. Simply dropping the poorly formulated 'add underscore' rule which only currently exists on the procedural interface and tidying up the mistake caused by that produces a MUCH shorter list of changes and allows much better consistency with even the existing OO interface elements? I look at the 'tidy' gd interface and simply think 'what the ****' Yes there are some inconsistent names, but in general imagecolorallocate and $image->colorAllocate is more in keeping with the other graphics libraries. YES there is room to create a more consistent procedural interface, but my original question still applies "consistent with what rules?" -- 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