Re: Consistent function names
| From: | Yasuo Ohgaki | Date: | Thu, 05 Mar 2015 08:44:38 +0000 |
| Subject: | Re: Consistent function names | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-84325@lists.php.net to get a copy of this message | ||
Hi Christian,
On Thu, Mar 5, 2015 at 4:34 PM, Christian Stoller <stoller@leonex.de> wrote:
> From: yohgaki@gmail.com [mailto:yohgaki@gmail.com] On Behalf Of Yasuo
> Ohgaki, Sent: Thursday, March 05, 2015 7:21 AM
>
> > 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.
> >
>
> Changing ctype_alpha to isalpha would be inconsistent with is_numeric.
>
I'm not going to change ctype_alpha to isalpha, but add IEEE complied name
alias. So the manual page would have ctype_alpha as the main function,
isalpha as IEEE complied alias.
BTW, I'm going to get rid of aliased/deprecated function listing. So aliases
and deprecated functions will not be listed, but only searchable.
For example, http://php.net/manual/en/book.ctype.php will not
be changed.
http://php.net/manual/en/book.classobj.php
will not list deprecated
call_user_method_array and call_user_method (or listed separately)
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net