Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84260
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F5895D.3090002@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> <54F4EBEC.2090702@garfieldtech.com>
 <CAGa2bXaQ0SgLWdv7WCoo_qyOQH=t2Vi_bwpk7qXZDEUk+7S7ew@mail.gmail.com>
 <54F4F3FC.6060501@fischer.name> <CAGa2bXb-d7A3So8e76=p5qqxrZgLK2B_4RKA1OKg0nHZiw9z6A@mail.gmail.com>
 <54F4FDFB.8010701@lsces.co.uk> <CAGa2bXZUvJJVDVj-48qpPuMas12fnDigKGcE-r=TK20Sahyi7w@mail.gmail.com>
 <54F5895D.3090002@gmail.com>
Date: Wed, 4 Mar 2015 03:54:56 +0900
Message-ID: <CAGa2bXbuNEcvoeeBhkUUEkiHZJFvJTVX=h_JPTLHpMTtgbCokw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1142e968590054051066e141
Subject: Re: [PHP-DEV] Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1142e968590054051066e141
Content-Type: text/plain; charset=UTF-8

Hi Rowan,

On Tue, Mar 3, 2015 at 7:13 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> Yasuo Ohgaki wrote on 03/03/2015 04:01:
>
>> Hi Lester,
>>
>> On Tue, Mar 3, 2015 at 9:19 AM, Lester Caine <lester@lsces.co.uk> wrote:
>>
>>  On 02/03/15 23:54, Yasuo Ohgaki wrote:
>>>
>>>> This looks awful... just cannot put up with...
>>>>
>>> Rasmus has already answered, but are you prposing to rewrite ->
>>> http://www.gnu.org/software/gettext/manual/gettext.html
>>>
>>
>> I know we used to have had copy of C library names.
>> I already explained why it looks awful. It violates coding standard and
>> sitting in PHP for more than a decade as it is.
>>
>
> You keep mentioning this coding standard like it's the Holy Bible. Coding
> standards are only as useful as the problem they're trying to solve, and
> there can always be justified exceptions to the rule.
>
> I doubt most PHP users look at that list of functions and think "tsk, tsk,
> the PHP devs didn't follow their own coding standards". They might think
> "why are these functions named the way they are?", in which case Rasmus has
> provided the answer, in terms of "vertical consistency" with cross-language
> libraries.
>

First of all, I'm not blaming anyone who named functions that violates
coding standard.
It was ok name them like this. I would name after under laying library
functions also.

If the cost of having consistent name is too high (too much cpu/mem/etc) ,
I would not
propose to add standard confirming names.  What I'm proposing is

"How about maintain legacy APIs to keep up with coding standard and have
consistent names?"

More or less, we do need maintenance, otherwise phpversion() will remain
inconsistent
forever. IMO.

I fully understand your arguments/reasoning, but I fails to see why not
having aliases to
have shiny procedural APIs for major version up...

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1142e968590054051066e141--