Re: async/await - is future reserved words in PHP 7.x?
| From: | Johannes Schlüter | Date: | Tue, 29 Sep 2015 12:20:44 +0000 |
| Subject: | Re: async/await - is future reserved words in PHP 7.x? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-88542@lists.php.net to get a copy of this message | ||
On Tue, 2015-09-29 at 08:49 +0200, Kalle Sommer Nielsen wrote:
> Hi
>
> 2015-09-29 7:30 GMT+02:00 Pierre Joye <pierre.php@gmail.com>:
> > This model totally failed for us in the past. And given that these keywords
> > will be used for anything related to async APIs, let reserve them and put
> > our users on the safe side already.
>
> While I understand the concern, I don't think we should just go
> reserve a bunch of keywords if there is no concrete plan an
> implementation model, maybe an RFC is having more no votes than yes
> votes etc, and we are stuck with 2 keywords that won't be used for
> another few years at least
I wouldn't block them in the parser. We however could list them in the
naming guide http://php.net/manual/en/userlandnaming.php
but for keeping
this relevant we have to maintain that page :)
Async/multi-threading functionality can also be built without keywords
using a "future" or "promise" model like C++ or JavaScript.
johannes
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc