Re: async/await - is future reserved words in PHP 7.x?

From: Date: Tue, 29 Sep 2015 22:22:26 +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-88572@lists.php.net to get a copy of this message
On Tue, 2015-09-29 at 11:29 -0700, Sara Golemon wrote: > On Mon, Sep 28, 2015 at 10:30 PM, Pierre Joye <pierre.php@gmail.com> wrote: > > 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. > > > Like that time we reserved use way before namespaces made it > into > the language? Just for history: Actually we didn't reserve "use" on purpose. In commit 5463dd5b in November 1999 Andi implemented a "use" feature which worked like require_once, which was introduced later. The feature was removed but unused "use" was kept by accident. In 5.3 we decided to use this unused keyword instead of adding a new keyword. https://github.com/php/php-src/commit/5463dd5b387298a84736e590e5d213f5bafe9435 We never purposely introduced a keyword. Only comparable thing was backporting a the b"" prefix for binary strings from meanwhile abandoned PHP 6 to 5.2(?).for forward compatibility. That has proven to be useless. Again an indication not to add async/wait keywords *now* as placeholder. :-) johannes

Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
« previous php.internals (#88572) next »