Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84608 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87841 invoked from network); 12 Mar 2015 02:08:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2015 02:08:44 -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:59367] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/C4-64353-A25F0055 for ; Wed, 11 Mar 2015 21:08:43 -0500 Received: (qmail 32644 invoked by uid 89); 12 Mar 2015 02:08:39 -0000 Received: by simscan 1.3.1 ppid: 32638, pid: 32641, t: 0.0860s 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; 12 Mar 2015 02:08:39 -0000 Message-ID: <5500F527.1030606@lsces.co.uk> Date: Thu, 12 Mar 2015 02:08:39 +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: <54F83C4D.1020206@gmail.com> <54F8BF67.6080600@gmail.com> <848D3C19-DE29-4E5F-9B23-D87D3F4A9365@gmail.com> <54FB45D6.3040803@gmail.com> <54FCD063.4040300@gmail.com> <54FEB910.5000608@lsces.co.uk> <54FF5E39.7000507@lsces.co.uk> <550035F0.10703@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 11/03/15 22:44, Yasuo Ohgaki wrote: > Having namespace for internals would bring much flexibility for API changes, both > OO and procedural API. I may try my best to have consensus. > > I think you also like to have OO style API for basic > variables(int/float/array) as I am. > Unless we have good/proper procedural API names, it would be an obstacle to > have OO style API for basic variables. I wish you agree to do something for it. Personally I just want to keep the current name set and so the sheer volume of changes proposed is a big kick in the face to me. People are talking about the need for an OO based interface, but there has been no comment by anybody as to how that should be styled. Having switched everything to camelCase as part of the E_STRICT reworking that is already well established so while I can see why you want to complete a complete switch to underscore padded names THAT is not consistent with what everybody else is already using? There should not be two naming styles running in parallel and that is all I am objecting to. If you get support for this RFC then both an extended namespace name set and OO based objects should all follow the same rules, and THAT is not what has been happening? I think it is equally valid to ask if the current naming guide IS still appropriate or if a switch to camelCase for every name space is more practical moving forward. In which case dropping the extra underscores makes more sense than adding hundreds more! That a name can be written all lower case, all upper case or any combination is more a matter of choice, but as you say error messages adopt a standard that may not match what is in the code anyway? -- 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