Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84201
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.53 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F4E93C.80206@gmail.com>
References: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.com>
 <CAEZPtU41xa1yrLPYn_VHx-axOmuM4_KAa00zwPRhpm5ZLSbQ+Q@mail.gmail.com>
 <CAGa2bXZD1MJojzFu8FwmGKH7gZxpqP7bNUusgQ3YzEpBduCs_g@mail.gmail.com>
 <CAEZPtU6=KY2tzRE8yw6kEdh4SrVJ3uG81XX5yuu0E_63G1HN6g@mail.gmail.com>
 <54F4E29D.7080501@garfieldtech.com> <CAGa2bXbph51CUHr_G87FL65hSDfLSDHo14Bnke-vaLu7SmH=ZQ@mail.gmail.com>
 <54F4E93C.80206@gmail.com>
Date: Tue, 3 Mar 2015 07:59:28 +0900
Message-ID: <CAGa2bXY45XX9Mgf+AKDUFccUbgxR-tBymBB2ow_mwCJyBOLW2A@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134ef8cffc6d50510562df2
Subject: Re: [PHP-DEV] Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1134ef8cffc6d50510562df2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Rowan,

On Tue, Mar 3, 2015 at 7:50 AM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 02/03/2015 22:36, Yasuo Ohgaki wrote:
>
>> I like scalar objects, but it does not resolve that PHP has non standard
>> function names.
>> It does not change old names, therefore it's impossible to resolve issue=
.
>> This is the reason why I'm proposing while I like scalar object, use of
>> namespace, etc.
>>
>
> Again, you're contradicting yourself here - you can't say that your
> mission is to change the old names, rather than offer an alternative, but
> then also say that the old names will stay around forever. If both names
> exist, that's exactly what you've created - an alternative.
>

I think there is big difference between new API and alias.
Alias is just a copy, new API works differently.


> If we're going to have an alternative, let's come up with a creative
> alternative that actually has an advantage to using it, not a choice
> between equally cryptic names like "strripos" vs "str_ripos".


I don't like the name neither. I improved other names such as
"array_sort_assoc_reverse =E2=86=92 arsort" ,
but I kept cryptic libc names.

Suggestions are appreciated for cryptic names.
I think "gettext_d" is equally bad, for example...

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1134ef8cffc6d50510562df2--