RE: [PHP-DEV] Reserve even more type hints RFC
| From: | François Laupretre | Date: | Thu, 30 Apr 2015 09:03:40 +0000 |
| Subject: | RE: [PHP-DEV] Reserve even more type hints RFC | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-86082@lists.php.net to get a copy of this message | ||
> De : Christoph Becker [mailto:cmbecker69@gmx.de]
>
> Relying on documentation only seems to be insufficient to me. Consider
> a developer not reading the documentation and facing the issue that
> his/her code might break with PHP 7.1 (i.e. a minor version).
+1. I already asked if we should enforce reserved names by a message and most replied that
documentation was enough. This is the lazy (I could say 'political') option and can only
lead to bad surprises when we decide to use the names. At this time, saying "People should have
read the doc" won't help them in any way, especially if their code dates back from before
7.0, when this doc didn't exist yet.
We don't need a warning there, we need a fatal error. These names are *invalid* as class names.
Regards
François