Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84189
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.171 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Tue, 3 Mar 2015 06:52:03 +0900
Message-ID: <CAGa2bXai0cXrqeq3X2vTV8CjseAp=CUY29YaaxKniZENw0-x4g@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113a9a64ebb59c0510553cc1
Subject: [RFC] [DISCUSSION] Consistent Function Names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a113a9a64ebb59c0510553cc1
Content-Type: text/plain; charset=UTF-8

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_to_be_renamed

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a113a9a64ebb59c0510553cc1--