Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84193
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXZD1MJojzFu8FwmGKH7gZxpqP7bNUusgQ3YzEpBduCs_g@mail.gmail.com>
References: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.com>
	<CAEZPtU41xa1yrLPYn_VHx-axOmuM4_KAa00zwPRhpm5ZLSbQ+Q@mail.gmail.com>
	<CAGa2bXZD1MJojzFu8FwmGKH7gZxpqP7bNUusgQ3YzEpBduCs_g@mail.gmail.com>
Date: Mon, 2 Mar 2015 14:01:21 -0800
Message-ID: <CAEZPtU6=KY2tzRE8yw6kEdh4SrVJ3uG81XX5yuu0E_63G1HN6g@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Consistent function names
From: pierre.php@gmail.com (Pierre Joye)

On Mon, Mar 2, 2015 at 1:58 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Hi Pierre,
>
> On Tue, Mar 3, 2015 at 6:40 AM, Pierre Joye <pierre.php@gmail.com> wrote:
>>
>> On Sun, Mar 1, 2015 at 3:29 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>> > 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?
>>
>> I see no gain to do that. It also won't solve the arguments order mess.
>>
>> The last time we discuss this topic the idea was to go for the new
>> pseudo object for most scalar, something Nikita worked on with a
>> prototype, allowing something like $mystring->replace(...); But adding
>> name aliases only to get names_defined_correctly sounds like a bad
>> move to me.
>
>
> Sadly, this proposal only renames functions and has aliases for old names.
> We may try to fix argument order mess when we have "default namespace"!
> I just don't have time to do all the job at once...
>
> I posted [RFC][DISCUSSION] as new thread. Please look at the list of rename
> candidates. I think you'll agree to rename most of them.

Sorry, I do not see how a new thread helps. Namespace either. These
will only be duplicated APIs for little to no gain. Existing codes
won't move as they won't be compatible with 5.x.

We should really consider Nikita's experiment instead,as it acutally
brings some big plus. Simple aliases for the sake of having _ in the
names bring nothing but confusion in my humble opinion.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org