Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69079
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BLU0-SMTP120B69BA7C5BC348F5D05DDE2390@phx.gbl>
References: <BLU0-SMTP120B69BA7C5BC348F5D05DDE2390@phx.gbl>
Date: Thu, 12 Sep 2013 08:43:30 +0200
Message-ID: <CAMyk_AY4Soqr9AdSaH9t_JiBwGmB=FVvSQxuDNc-7YQ5=K6xEQ@mail.gmail.com>
To: Bob Weinand <bobwei9@hotmail.com>
Cc: Developers List PHP Mailing <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b15fbcf8445a104e62a0fa8
Subject: Re: [PHP-DEV] Support for keywords where possible
From: linepogl@gmail.com (Lazare Inepologlou)

--047d7b15fbcf8445a104e62a0fa8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2013/9/11 Bob Weinand <bobwei9@hotmail.com>

> 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 wil=
l
> 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
> =3D> $value); instead of the until now necessary func("array" =3D> value)=
;
>
> You can find the patch here:
> https://github.com/php/php-src/pull/438
>
> Any thoughts about this?
>
>
>
I like it! I always hated the fact that "list" is a reserved word.

Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel

--047d7b15fbcf8445a104e62a0fa8--