> -----Ursprüngliche Nachricht----- > Von: julienpa...@gmail.com [mailto:julienpa...@gmail.com] Im Auftrag von > Julien Pauli > Gesendet: Donnerstag, 26. Februar 2015 10:27 > An: Dmitry Stogov > Cc: Alexander Lisachenko; PHP internals list > Betreff: Re: [PHP-DEV] [Discussion] Last chance for case-sensitive engine > > On Wed, Feb 25, 2015 at 7:52 PM, Dmitry Stogov <dmi...@zend.com> wrote: > > > Hi Alexander, > > > > On Tue, Feb 24, 2015 at 10:48 AM, Alexander Lisachenko < > > lisachenko...@gmail.com> wrote: > > > > > Morning! > > > > > > I want to ask this question one more time before PHP7 feature > > > freeze: can we the engine case sensitive from PHP>=7.0? > > > > > > There is a draft for that: https://wiki.php.net/rfc/case-sensitivity > > > (mostly empty), so I decided to ask this question in the internals > > > mail list. > > > > > > Pros: more simple O(1) hash table checks for properties, functions, > > > methods, classes without strtolower normalization on the > > > engine/parser level. Consistency with unicode class names (yes, they > > > are case > > sensitive, > > > check http://3v4l.org/ia0pc), consistency with exisiting PSR0,4 > > standards > > > (case sensitive mapping of class names to the file names) > > > > > > From my experience, all modern PHP framework don't use > > > case-insensitive code, so chance to break anything for them is really low. > > > > > > Cons: on the extension level things aren't so good and can be some > > > BC breaks (like with phpng) > > > > > > Possible ways: > > > > > > 1) Keep PHP engine case-insensitive for PHP7 > > > 2) Make PHP engine case-sensitive since PHP7 with possible minor BC > > breaks > > > in the extensions (this breaks can be easily fixed) > > > 3) Add a compile-time switch, eg. --with-case-sensitivity to the > > > configuration to have an ability to build PHP with sensitivity and > > > make this option enabled by default since next major version > > > (PHP>=8.0). Add deprecation notices in 7.x > > > > > > Thoughts? > > > > > > > I case we would designed a new language I would rise two hands. > > Changing, syntax in an existent widely used language is an additional > > pain for users. > > Technically it shouldn't be very difficult to remove support for > > case-insensitivity, and it'll even improve speed and memory > > consumption, but I don't think it costs the compatibility break. > > > > Thanks. Dmitry. > > > > I agree that doesn't seem like a reasonable idea. > > Julien.P
I also agree, I think that is something for a static code analyser to rant about -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
