Re: Case insensitivity weakened the power of overloading

On Sun, 18 May 2003, Zeev Suraski wrote: > At 16:29 18/05/2003, Wei He wrote: > > >Just I want to know the reason not doing CS. > > Simply put, backwards compatibility. If PHP was released today, it would > have been case sensitive. And yes, there are plenty of other people, some > on this list and many that aren't, that object to going to case sensitivity > because of this reason exactly. So it does? Then as I think PHP's backwards compatibilty records really needed to be criticized. A more item won't make it worse. :) Even though there are better ways of doing this rather than lowercasing all class/function names before adding to the hash. As least __call should have been able to get the case-sensitive method name. IMO it's quire unnecessary to close the CS thread. > By the way, if what you worry about is bridging with external object models > like Java, COM or GTK - you don't have to worry. Only PHP objects are case > insensitive. The OO overloading layer in ZE2 supports case-sensitive > method calls. That sounds good to me. But I still suggest being CS in ZE2 even for PHP objects. There is a Chinese saying, better short pain than a longer one. You can just go ahead to do CS in ZE2. Nobody will die of it and only PHP becomes more mature. Best, Wei He