Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXZJoyV+9qN6v8j3+vHexoqDtHR4cZkgdtdc1GpVkDaD9w@mail.gmail.com>
References: <CAGa2bXZJoyV+9qN6v8j3+vHexoqDtHR4cZkgdtdc1GpVkDaD9w@mail.gmail.com>
Date: Thu, 23 Jan 2014 07:17:25 +0900
Message-ID: <CAGa2bXY4=3UVDVdR=curS96r=pvTrxDYA0wgy+k7X46omtTPgQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01227c0cbc3a1a04f0967fcf
Subject: Re: [PHP6] Function name consistency
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e01227c0cbc3a1a04f0967fcf
Content-Type: text/plain; charset=UTF-8

On Sat, Dec 28, 2013 at 3:57 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> I know this has been discussed before, but I'll try again.
> We have following coding standard
>
> 1.  Function names for user-level functions should be enclosed with in
>     the PHP_FUNCTION() macro. They should be in lowercase, with words
>     underscore delimited, with care taken to minimize the letter count.
>     Abbreviations should not be used when they greatly decrease the
>     readability of the function name itself::
>
>     Good:
>     'mcrypt_enc_self_test'
>     'mysql_list_fields'
>
>     Ok:
>     'mcrypt_module_get_algo_supported_key_sizes'
>     (could be 'mcrypt_mod_get_algo_sup_key_sizes'?)
>     'get_html_translation_table'
>     (could be 'html_get_trans_table'?)
>
>     Bad:
>     'hw_GetObjectByQueryCollObj'
>     'pg_setclientencoding'
>     'jf_n_s_i'
>
> https://github.com/php/php-src/blob/master/CODING_STANDARDS
>
>
> There are many functions that violate this for historical reason.
> Since PHP has function alias feature by default, function names that
> violate this standard could be renamed and keep historic names as aliases.
>
> We may keep alias 10 or 20 years or even forever.
>
> Good IDE can suggest correct names, but keeping inconsistent historic
> function names forever damages PHP future in the long run, IMHO.
>
> Any comments?
>

Added RFC for this.

https://wiki.php.net/rfc/consistent-names

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e01227c0cbc3a1a04f0967fcf--