Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84318
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.45 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F7E61B.4040301@lerdorf.com>
References: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.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> <CAGa2bXbuNEcvoeeBhkUUEkiHZJFvJTVX=h_JPTLHpMTtgbCokw@mail.gmail.com>
 <554F0C3F-770F-4694-A5AB-FDC54FCCBF00@gmail.com> <CAGa2bXbDdS=N=JmPwBa1iorx1aJPuo00EfU7bw31cknAxAfDyQ@mail.gmail.com>
 <CAEu+QUX1j2P+OfU+Sf_wUOQzYrLody0zPF6V9rVWvYjGFfbrSg@mail.gmail.com>
 <CAGa2bXZYG37qdkjTkoDq12GtYTwS-=gX-=msPx3RWeSenxSdqw@mail.gmail.com>
 <54F72360.6000702@lerdorf.com> <CAHXmDMAwuxHtBU1DV_g_FwPKc9TfDcyJrX=+WEMXZevmbmQftQ@mail.gmail.com>
 <CAFp73Xs4-Py+g0KuP2YwhZU7v2fiSV+vHoa9UU=7MY881m+Ycw@mail.gmail.com>
 <54F73702.9050806@lerdorf.com> <CAGa2bXahda2KfdFXJZakTy0ey0yk-R5wwKOPotOQ_mLfm3dwfw@mail.gmail.com>
 <54F7E61B.4040301@lerdorf.com>
Date: Thu, 5 Mar 2015 15:21:22 +0900
Message-ID: <CAGa2bXb+t+p8uGYRQ13k4F7vOJ85=uSw1y-7=S9ZnWpy3bYjjw@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11406c9a0799c005108496ee
Subject: Re: [PHP-DEV] Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11406c9a0799c005108496ee
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Rasmus,

On Thu, Mar 5, 2015 at 2:14 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> Every function name defined by IEEE Std 1003.1 along with the arguments
> and argument order would be on that list. When we have procedural
> functions that are either thin wrappers around or otherwise behave
> identically to an IEEE 1003.1 defined function, then the name and
> arguments currently match that specification quite well. Any deviation
> should have a really really good reason.
>
> You can find the full list here:
>
> http://pubs.opengroup.org/onlinepubs/9699919799/idx/is.html
>

I like the idea to be IEEE 1003.1 compliant. I'm used to these name too.
If anyone don't mind, I would like to extend scope of the RFC to have
both PHP and IEEE names and document them.

For example, ctype extension has "ctype_" prefix. It replaces "is" to
"ctype_".
we may have "isalpha" alias as IEEE compliant name. There are many
IEEE confirmed names already. Only small adjustments are needed.

Document may look like

http://php.net/manual/en/function.ctype-alnum.php
----------------------------
 ctype_alnum
 Aliases
  - isalnum (IEEE 1003.1)   <- There is no "isalnum" defined in PHP
currently.

(PHP 4 >=3D 4.0.4, PHP 5)
ctype_alnum =E2=80=94 Check for alphanumeric character(s)

Description =C2=B6

bool ctype_alnum ( string $text )
Checks if all of the characters in the provided string, text, are
alphanumeric.

Parameters =C2=B6

text
The tested string.

Return Values =C2=B6

Returns TRUE if every character in text is either a letter or a digit,
FALSE otherwise.
----------------------------

The same could be done for new names.
Manual pages for localtime()/mktime()/etc would look a lot nicer.
I hope there will be more favored developers with the RFC. Since I'm going
to
update manual to have alias search feature, developers used to POSIX can
find
PHP function name easily. If they would like to use POSIX name, they can us=
e
it also. Nobody will try to remove POSIX names in the future, I suppose.

In short, I would like to propose to have both PHP and IEEE names as
officially
valid names. Do you like this proposal?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11406c9a0799c005108496ee--