On 11/09/01, "Cristopher Daniluk" <[EMAIL PROTECTED]> wrote:
> Still, the option of
> introducing runtime function aliases and/or compiler directives was brought
> up. I personally prefer this solution, its not a bad idea for PHP to have
> anyway, and gives users a ONE LINE solution, while giving the rest of PHP,
> the overwhelming majority mind you, a more consistent language.
>
> Clearly, no one loses in this scenario. The small chunk who use gettext make
> a one line change. Performance is not affected. Conventions are satisfied.
> Everyone goes home happy. What's the problem?
There isn't one (as I have been saying all along).
But it doesn't really change the fact that code that uses gettext will
still have _() everywhere, and we will still have the "problem" of people
saying "wtf does _() mean? I can't find it in the manual??" which is the
basis of this whole argument.
Let's do this alias thing, but lets also document _() for the sake of
those people that have never heard of gettext but need to maintain the
code.
--Wez.
The world needs more engineers
--
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]
