On 08/09/01, "Zeev Suraski" <[EMAIL PROTECTED]> wrote:
> At least give the user the option to decide whether he wants to pollute his
> namespace. At least give the code readers a chance to figure out what's
> going on by grepping the PHP source code. Sending them to the C source
> code or to debuggers is the old style thinking of PHP. Most new comers to
> PHP today have no C knowledge.
The user gets the choice of polluting their namespace by compiling in the
gettext extension.
Are you really serious when you say that you want to deprecate _()??
Just think how many of the "bigger guys" will be affected and seriously
pissed that their nicely localized enterprise application suddenly doesn't
work or drops its performance several notches ?
Yes, I know it's not nice, but it's the unnofficial standard.
Lets think about this:
_() is only there if you compile in the gettext extension.
_() is recognized by all gettext users as being an alias for gettext()
You say that _ should not be used for anything in the language or
on it's own.
So it's never going to collide with anything else
You say that if you come across it and wonder what it does, the manual
doesn't tell you what it is. Lets solve that by putting it in the manual.
I don't think it's such a big deal.
--Wez.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
