I plan to move this rfc forward to voting phase in the next days.
I have made some (huge) changes to the initial implementation over the last weeks.
There initially was the problem that there were some ugly restrictions which keywords are allowed
under which circumstances.
They are now resolved (= all keywords possible except the ones which conflict with existing
functionality).
If there aren't any further objections now, I'll move it to voting phase.
Bob Weinand
Am 11.9.2013 um 23:21 schrieb Bob Weinand <[email protected]>:
> Hi!
>
> I tried to widen the naming possibilities by allowing to use keywords as identifiers (for
> function names, class names, label (goto) names, ....) where possible. It doesn't break any BC.
>
> 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 also prevents unnecessary workarounds like in https://wiki.php.net/rfc/named_params#syntax.
> There, to address a function with a parameter called $array, we could simply write func(array =>
> $value); instead of the until now necessary func("array" => value);
>
> You can find the patch here:
> https://github.com/php/php-src/pull/438
>
> Any thoughts about this?
>
> Bob Weinand