Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84102
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.43 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Sun, 1 Mar 2015 20:29:49 +0900
Message-ID: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c03a7ec263170510386dbd
Subject: Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c03a7ec263170510386dbd
Content-Type: text/plain; charset=UTF-8

Hi all,

First of all, I have no intention removing old function names.

PHP function names are subject of critics for a long time.
http://www.phpsadness.com/sad/4
http://www.phpsadness.com/sad/15
http://www.phpsadness.com/sad/27

How about rename all of these functions according to CODING_STANDARD for
PHP7
and have aliases for old names? Some names need complete rename, but most of
them are matter of adding "_".

Function names like phpversion(), htmlentities(), image*() shouldn't be
kept. IMHO.
(I repeat. I have no intention removing old names)

str*() would be most difficult. How about rename all of them to str_*()?
and keep
libc compatible alias names forever?

Thoughts?

It's last chance for PHP7.
Sorry that I bring up this topic again, but I couldn't resist.
If there isn't many objections, I'll write RFC and do all the work needed.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c03a7ec263170510386dbd--