On 10/30/2010 01:30 AM, Rasmus Lerdorf wrote:
On 10/29/10 11:17 PM, Chad Emrys wrote:
The fact they have to google to figure out what it means, the error
message fails at it's purpose. (Realistically it'll take longer than a
second unless you got google hot keyed to your log reader). I Liked
Stefan's idea in the previous thread to not put token names in the error
messages anymore and replace them with something more meaningful for the
user. However, since that never happened, this is a better/easier
alternative for now. How many total hours of googling will we save
developers for a 10 sec grep and replace? (not sure if it's that easy,
but for the sake of the argument).
I can see only positives by switching it out. can someone give me a
light on how much it would actually cost to do that? Some negatives? I
don't see the argument given to be entirely helpful because it's exactly
what I am trying to point out as a problem, and the reason why we should
change it.
There are two reasons this term will stay. It is a tip of the hat to
the amount of PHP work that came out of Israel, and it is a good
reminder that there are a lot of other languages in the world. People
whose first language is not English, myself included, are forced to work
with unfamiliar terms every day. I wouldn't mind having a few more
non-English identifiers in PHP actually.
Well, and a third reason, I like it.
-Rasmus
Well Rasmus, I wish you would hang out more in ##php on freenode. (I
see you there every so often) But we do get that question about that
thing a lot. And even some rage, and I have to cool them off with all
the reasons you and Andi are giving me right now. But I am not
convinced nostalgia or "teaching the English speakers a lesson" is a
good reason to keep around a confusing error message.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
