Zeev Suraski wrote:
>
> > Did/do you use gettext in other languages?
>
> No
>
> >If the answer to the latter, at least, is 'no' then I think the
> >experience of people like Rasmus and Chuck -- who *do* use gettext
> >a lot, and in other languages -- carries a helluva lot more weight
> >than your speculation and that of other non-gettext-users.
>
> I respectfully disagree. The issue here isn't about people who use
> gettext. It's about those who don't.
Eh? So you do not mind making a feature harder for the people
who use it, just because it makes more sense to the people who
do not? ???
> Moral - the obscurity of such a feature should be determined by
> the general public, and *NOT* by the ones who use it.
Okey, determine that it is obscure. Determining that and removing
it are two different things. I do not mind if you label it as
obscure; I *do* mind you, who never use it, making it much more
difficult for the people who do. Live and let live, don't try
to force people into your mould.
> Did you look at the deprecation method I suggested?
Yes. It boils down to taking something away from your users.
Now or later, that is still what it is doing.
Your argument seems to be that _() is obscure for people who
happen to come across it, or have to suddenly maintain something
that uses it. The userland function solution does not change
that. My opinion: let them deal with it. They are and probably
will remain a minority compared to those who actually actively use it.
How long has it taken you, one of the in-depth-est PHP developers,
to notice this? The effort required for them to find out what it
does, compared to that required by current users to change the
way they work, seems very heavily weighted toward the latter.
MHO, of course.
When I encountered this whilst tech-editing PHP Essential Reference,
my reaction was, 'Cool! What a low-impact way to do I18N!' And
I kid you not, that is really how I felt, and feel.
> The problem with this whole discussion is that people are mixing
> two issues:
> (a) Is it an ok thing that _() is a PHP function
I say that it is perhaps unfortunate, but okey.
> (b) What can we do about removing it
That only comes up if people answer 'no' to (a).
Hey, I am not a member of the PHP group. I am just a user.
Never mind that I have been writing software for more than
a quarter-century. You guys are going to do whatever you're
going to do, and the only effect my differing opinion is likely
to have is to piss everybody off. So I'll stop arguing and
let you get on with it.
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
"All right everyone! Step away from the glowing hamburger!"
--
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]
