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. Zeev At 01:01 PM 2/6/2002, Marko Karppinen wrote: > >> However, we need vote for if PHP5 will have case > >> sensitive class/function/constant names. > > > > +1 for case-sensitive everything > >-1. Differentiating two objects only by the case of their names >seems absurd to me. This is not how humans function. > >Ease of implementation is the only thing speaking for case-sensitiveness in >my book. Case-insensitiveness is always more work. But I think it's well >worth the trouble. > >Hence case-insensitive, case-preserving is my suggestion. > >--Marko > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
