At 06:04 PM 2/6/2002 -0600, Jason Greene wrote: >On Wed, 2002-02-06 at 10:13, Zeev Suraski wrote: > > While I agree with Marko's vote (I'm also very much against it), I derive > > my conclusion from a whole different perspective. > > > > Guys, we are not next to the drawing board right now. The specs were > > defined and the layout was laid years ago. At this point in time we're > > only supposed to change something like that if there's an overwhelming > > reason to do it, and none of the reasons mentioned falls into that > category. > > > > The reasons to move to case sensitivity and the alternative ways we should > > handle them, in my opinion, are: > > > > - Speed. We can probably improve the typical case so that it's not any > > slower in runtime. > > - Interaction with external component systems - we can have case > > sensitivity implemented at the module level, especially with the Engine 2 > > infrastructure, and still remain case insensitive for regular PHP objects. > > - "It's just right". Well, I can totally agree with that, but only if we > > were next to the drawing board, which we're not. > >You left off language consistency between variable names, and function >names. > >We are already completely redesigning OO which is like standing at the >drawing board.
Engine 2 will not break scripts that badly (at least not in my opinion). The OO stuff is mainly adding new functionality. Changing function names will break scripts badly. There's a huge difference. Andi -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
