Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84208
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.51 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F4F3FC.6060501@fischer.name>
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>
Date: Tue, 3 Mar 2015 08:54:21 +0900
Message-ID: <CAGa2bXb-d7A3So8e76=p5qqxrZgLK2B_4RKA1OKg0nHZiw9z6A@mail.gmail.com>
To: Markus Fischer <markus@fischer.name>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1142ea8a4536ab051056f27d
Subject: Re: [PHP-DEV] Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1142ea8a4536ab051056f27d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Markus, Larry and Rowan,

On Tue, Mar 3, 2015 at 8:36 AM, Markus Fischer <markus@fischer.name> wrote:

> On 03.03.15 00:10, Yasuo Ohgaki wrote:
> > I would love to have new & clean APIs.
> >
> > Please think my proposal as legacy API cleanups. Many of candidates wil=
l
> > remain
> > without CORDING_STANDARSDS confirmed names almost forever. This is what
> > I would like to improve. If you don't care about legacy stuff cleanups,
> > please don't
> > care. The cleanups will not hurt anything, almost.
>
> No ill intentions here, but adding the aliases and, as you propose,
> literally adding *hundreds* of aliases is actually a mess to me.
>
> What you call "new & clean" is as a shield for effectively introducing
> duplicates. You do not clean up anything that way. You leave a even
> bigger mess behind. By going for your honorable goal of correcting
> things I think you got lost in the woods.
>
> IMHO the only forward is to make sure new/future additions to the
> language adhere to the coding standard or use a smart way (i.e. the
> scalar addition).


I think I understand your point very well.
However, I have an urge impulse to add standard confirmed names
when I see manual pages like

http://php.net/manual/en/book.gettext.php
bind_textdomain_codeset =E2=80=94 Specify the character encoding in which t=
he
messages from the DOMAIN message catalog will be returned
bindtextdomain =E2=80=94 Sets the path for a domain
dcgettext =E2=80=94 Overrides the domain for a single lookup
dcngettext =E2=80=94 Plural version of dcgettext
dgettext =E2=80=94 Override the current domain
dngettext =E2=80=94 Plural version of dgettext
gettext =E2=80=94 Lookup a message in the current domain
ngettext =E2=80=94 Plural version of gettext
textdomain =E2=80=94 Sets the default domain

This looks awful... just cannot put up with...

PHP is evolving as a modern language, but these manual pages/functions
make me feel PHP as a legacy language. I wish I'm alone who feels this way.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1142ea8a4536ab051056f27d--