> De : Andrea Faulds [mailto:a...@ajf.me] > I’d thought of doing this before, but the backwards-compatibility cost is too > high.
It is a BC break, I agree, but would the impact on PHP community be so high ? I have never seen any PHP code which would rely on function/class names case-insensitivity. I tested this with Automap, a map-based autoloader, modified to work in a case-sensitive manner. I tested most PHP frameworks and libraries and none of them had case mismatches. There are some, probably, but I guess that most, if not all, are undetected typos. Can't we consider such a mismatch as a bug ? That's what any normal programmer would think, IMHO. So, I think that such a BC break on a problematic syntax is acceptable, and would even help clean some PHP code. What we can do to minimize the BC break, in the spirit of the migration path discussed these last days, is to introduce an E_STRICT warning in version 5.7, which would help programmers prepare their code for PHP 7. Regards François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
