Re: Case insensitivity weakened the power of overloading

> > I'm personally sick and tired of living my life in a loop. Yes, there are > certain issues where there's a bunch of people on internals@ that would > like to see things changed, and you know what, they won't. Why? Because > that's the way they used to be, that's the way they were when you joined > the project, and those that forged this project believe that they're key > factors to the project's success, or that changing them would seriously > hurt the project in general. I can understand the feeling. But I don't think it is the right way that once a decision is made, it has to be follow for 1000 years. Regardig this issue, why not create a check list on the web, showing all the reasons to do and not to do. As the world is changing, one day people might aggree to be on one side or another. I think this is at least a better way to pull your life out of the loop. :) For PHP's success, I don't think it is because keeping things unchanged. On the country, the evolution is the key. Why I have spent 6+ years developing on PHP and have coded several hundreds of classes? Why not just go JAVA and forget the countless walkaronds on passing class instances by reference? Why not just stay on Zope rather than try to connect PHP to Zope? And I'm sure there are stronger reasons for other PHP lovers. Look at PHP's evolution, there are many big behavior changes affecting current codes. Some are important like register global vars and some IMO are unnecessary like calltime pass references. All these changes are trying to change the programmers' coding habit. And I don't think a single one of them will become angry on this (at the most, upset a little bit). I can see Zend Engine 2 has more problems regarding changing what it currently is. Like the function namespace. I have to go through my projects to rename Foo::count() to avoid otherwise unwanted effect when counting arrays. What my impression is, as this can be change, why not case sensitivity? Are there still someone object CS on this list besides you whose reason is a decision made 3 years ago? > A fundamental issue like case sensitivity falls in that category. So does > the decision to bundle key libraries, a decision reached by the PHP Group > in January 2000. When you joined the project, you acknowledged it was > something you were willing to live with. > The fact that people who care about these things are already fed up with > discussing them again and again, and that there are random majorities on > internals@ against them, is NOT going to change it. As I said once, when > is it time to end the discussion? Once we reach a decision that *you* are > happy with? Before you answer "Yes! :)", the answer is no! Will the changed behaviors like register global vars still lead to discussions? Sorry, I don't mean to give you, the one in such a sensitive position, any pressure. (Can this because CS will affect Zend's commercial products much more than end users' codes?) I can patch PHP myself and share it with any other one likes it. Just I want to know the reason not doing CS. Be relax, everyone. :) Wei He