Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84256 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68145 invoked from network); 3 Mar 2015 17:34:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Mar 2015 17:34:40 -0000 X-Host-Fingerprint: 77.193.237.4 4.237.193.77.rev.sfr.net Received: from [77.193.237.4] ([77.193.237.4:12774] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 31/A2-03783-CA0F5F45 for ; Tue, 03 Mar 2015 12:34:36 -0500 To: internals@lists.php.net Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes References: Date: Tue, 03 Mar 2015 18:34:19 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/1.0 (Win32) X-Posted-By: 77.193.237.4 Subject: Re: [RFC] [DISCUSSION] Consistent Function Names From: bensor987@neuf.fr ("Benoit Schildknecht") Hi, I think the new functions must have consistent parameters order too. I = think it is about the right time, so we'll have a cleaner and more logic= al = language. ATM, it's a real headache, we constantly have to read the documentation = to = make sure we give the arguments in the right order. For instance - implode() : "implode() can, for historical reasons, accept its = parameters in either order. " - strpos( $haystack, $needle ) - in_array( $needle, $haystack ) Regards. Le Mon, 02 Mar 2015 22:52:03 +0100, Yasuo Ohgaki a = = =C3=A9crit: > Hi all, > > First of all, I have no intention to remove nor deprecate old function= > names. > Old function names must exist for compatibility and should be able to = use > forever. > > We have CODING_STANDARDS[1] for a long time. > However, PHP has so many functions that do not confirm this. Many of > violating functions can have standard conforming names safely > > This RFC[2] proposes the CODING_STANDARDS confirmed function names. > The list[3] is almost complete, but improvement can be added. For = > example, > get_rusage() could be sys_get_rusage() because there is sys_getloadavg= () > already. > > There would not be much opinions for independent modules like BCMath, = GD. > Please take a look for others and give your comments. > > Thank you! > > [1] https://github.com/php/php-src/blob/master/CODING_STANDARDS > [2] https://wiki.php.net/rfc/consistent_function_names > [3] > https://wiki.php.net/rfc/consistent_function_names#list_of_functions_t= o_be_renamed > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net -- = Utilisant le logiciel de courrier d'Opera : http://www.opera.com/mail/