On 30-4-2015 11:03, François Laupretre wrote:
De : Christoph Becker [mailto:cmbecke...@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
It might be just me, but why don't we just throw an E_STRICT error?
Isn't that exactly what they are for? To warn the user about potential
problems that he can easily fix now before being bitten by it?
- Tul
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
