On Thu, Apr 30, 2015 at 12:41 AM, Christoph Becker <cmbecke...@gmx.de>
wrote:
> Hi everybody!
>
> I've noticed that the "Reserve Even More Types in PHP 7" RFC[1] has been
> moved to "Process and Policy" with the comment "needs no impl".
> However, the RFC states:
>
> | This RFC does not fully reserve them as keywords; it only prohibits
> | their usage as class, interface and trait names.
>
> In my opinion, this has to be enforced by throwing a fatal error
> ("Cannot use '*' as class name as it is reserved"), whenever one of the
> reserved identifiers (resource, object, mixed, numeric) is used as
> class, interface or trait name.
>
> 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).
>
> The "Backward Incompatible Changes" section appears to support my opinion.
>
> [1] <https://wiki.php.net/rfc/reserve_even_more_types_in_php_7>
I've moved the RFC based on Sara's mail in the voting thread [1]. Quoting:
> There's no language in the RFC about
> actually throwing errors or other code-breaking behavior. Therefore,
> even should all of them pass, it does *NOT* mean that your code using
> these names suddenly stops working on PHP7. It means that you have
> been warned that using the names of intrinsics is a bad idea, and that
> the language reserves the /right/ to make doing so an error at some
> point in the future.
I also know that at least some of the votes were cast under the assumption
that this is just a "documentation" reservation, as opposed to throwing
errors.
/cc Sara
Nikita
[1]: http://markmail.org/message/3zehjdlvuhv5sosq
