I guess so that we can have a language that will be able to model real world problems... instead of the real world changing the name of the problem to fit the language.
Language has its rules. Keywords are one of the rules. I, for example, am annoyed that in English you have to put this silly "a" and "the" everywhere, while so many real languages live perfectly well without it. If you want to argue how English is unfit to represent real world problems, reread "Who's on first base" sketch :) PHP has similar problems - some real world cases would have to add one or two letters so that it won't be confusing to the parser. Terrible, I agree, but that's what we have.
Or, how about creating a language thats always striving to be better..
Name one language that strives to be worse. Your better is apparently different from other's better and also from what's possible and feasible to do.
With the adoption of PHP5 also comes the increased adoption of OOP.. and this issue is a speed bump.
No it isn't. I can see no single serious reason why the class must be named Case or you have to move to Smalltalk or give up OOP altogether. It's a minuscule annoyance at best.
Anyway, I write so that perhaps, maybe, just maybe, someone might want to see whats involved instead of simply writing off this request....
What's involved is probably changing language parser, not sure even current flex/yacc combo can do it.
-- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
