> De : morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] De la part > > 1. I proposed making class names case-sensitive and it was clearly rejected, > most considering it is a *huge* BC break for almost no benefit. I personally > don't know any software which uses class names in a case-insensitive > manner but it seems others do ! I am not sure, but scalar type hints were > probably implemented as case-insensitive too. In other words, if you're > ready to relaunch the case-sensitivity discussion, feel free to do it. > > To be completely accurate, it was rejected *for PHP 7*. PHP 7 was > announced suddenly and rushed through. I think a BC break of this > magnitude in PHP 7 would be incredibly painful *because of the > timetable*. Whereas if we decide now that in PHP 8 all identifiers > will be case sensitive that's a different story because of the > timeline. Knowing years in advance that something will happen gives > you ample time to migrate (like we are doing with PHP 4 constructors > in the PHP 7 series; they are deprecated and support will be removed > in PHP 8).
Mmh, PHP 7 or not, the reaction was really : 'huge BC break for no benefit'. I'll try to propose it more in advance for 8.0, as you suggest, but I'm really not sure it has more success. Anyway, that's not a serious solution to solve type hint conflicts. Regards François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
