snipped... > > Check the history, every language developement tools which > tried to do it do not support it anymore. Why? For the exact > same reasons listed in this thread.
I am not sure why you say this. Java and other languages support multilingual identifiers. The newest standards for programming languages are including this feature. Also markup languages. (XML) > I'm no pollitician or geostrategy expert, but I do see that > english in a _programming language_ is a good thing. Now, > whether people does speak english or not is not the problem > and is not our problem. He says in english... ;-) I can speak german, french or english > while explaining code writing source codes using english > identifiers. And it's the same for many asian or russian > friends with their respective languages. But the only time I > tried to write code in french and I have had to explain it in > another language, it does not work out and it does not work > out for the other with other languages (was german and russian). ok, so you shouldn't program in french. For others it is fine and works better than english. > > I think you are just mixing end user applications requirement > (i18n) and programming language requirements. I don't think you have made a case for why it shouldn't be allowed. Only that you don't like it and it doesn't work for you. But nobody will make you use non-english terms, so it shouldn't be an issue for you. Let's agree to disagree. I don't think either of us is shedding much additional light here now. > > Regards, > > --Pierre Regards as well, tex -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
