Am 12.9.2013 um 22:59 schrieb Pierre Joye <pierre....@gmail.com>:
> On Thu, Sep 12, 2013 at 10:55 PM, Nikita Popov <nikita....@gmail.com> wrote:
>> Supporting different sets of keywords in
>> different locations is pretty confusing. Imho we should add this kind of
>> support only in places where a) we can support all keywords and b) it is
>> unlikely that supporting keywords there will cause issues in the future.
a) has the problem while we can now define a class List {} (<= allows all
keywords),
we cannot access List::const; (<= not all keywords are allowed here).
(To still access it, it would have to be an uglier namespace\List::const;)
See also https://github.com/php/php-src/pull/438 for which combinations of
keywords
are possible.
> b) can't be proofed, also the keyword problem being future ready is
> also a shiny myth. It is a moving target.
They actually aren't future ready for all cases; in my initial mail I wrote:
"Furthermore when BC needs to be broken in future for new keywords, it will
have a
__smaller__ impact as __most__ usages of the new keyword then still work."
It will only make the impact smaller; I didn't say that it will make disappear
any impact.
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
Bob Weinand
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
