RE: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7
| From: | François Laupretre | Date: | Tue, 28 Apr 2015 14:13:11 +0000 |
| Subject: | RE: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7 | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85996@lists.php.net to get a copy of this message | ||
> De : Dennis Birkholz [mailto:dennis@birkholz.biz]
>
> I would like PHP to make all class/trait/interface names case-sensitive
> and use only lower-case names for the scalar type hints (same for
> object, array, etc.). This would solve most problems. Class names are
> kind of case sensitive in applications that rely on autoloading on
> platforms with case sensitive file systems.
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.
2. Anyway, basing name conflict resolution on naming conventions is not acceptable, in my opinion.
PSR-1 is just a convention. We cannot resolve name conflicts in the core based on this. If we want
to go that way, let's display an E_STRICT message when encountering an all-lowercase class
name, but that's another debate and I don't think anyone is willing to enforce PSR rules
in the core.
Regards
François