Re: Consistent function names
| From: | Yasuo Ohgaki | Date: | Tue, 03 Mar 2015 00:15:07 +0000 |
| Subject: | Re: Consistent function names | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-84210@lists.php.net to get a copy of this message | ||
Hi Rasmus,
On Tue, Mar 3, 2015 at 9:03 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> These come from the underlying libaries. You can type "man dcgettext" or
> "man bind_textdomain_codeset" at your Linux command line and learn a lot
> about how these work. Plus, if you are a C dev, much like strlen(),
> these are simply the names you expect, or at least they are instantly
> recognizable to you. As I normally explain to people, there is vertical
> consistency here, not horizontal consistency.
>
> I understand how people who don't have a background in the underlying
> libraries might wish for a different API and horizontal consistency
> across disparate extensions, but simply adding a bunch of aliases that
> have no basis in anything doesn't help anybody.
>
I know where gettext function names come from.
If we write these legacy modules now, there will be modname_function() only.
Why couldn't we do it before PHP7?
I proposed the same before PHP5.
I'll probably do the same before PHP8 if we have legacy names still...
We can live without new names, so it's not too important. I just feel
somehow PHP being legacy/unmaintained when I see/use legacy
function names...
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net