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

From: Date: Tue, 29 Sep 2015 22:00:31 +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-88568@lists.php.net to get a copy of this message
I think, we don't need to reserve words, until we decide to implement this. The context sensitive scanner introduced in 7.0 makes the problem less serious. $ sapi/cli/php -r 'class foo { static function use() {echo "ok\n";}} foo::use();' ok Sara, related question... Is the semantic of async/await in Hack and Dart is the same? Thanks. Dmitry. On Tue, Sep 29, 2015 at 9:29 PM, Sara Golemon <pollita@php.net> 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? > > -Sara > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >

« previous php.internals (#88568) next »