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

On Wed, Sep 30, 2015 at 12:08 AM, Johannes Schlüter wrote: > On Tue, 2015-09-29 at 21:04 +0300, S.A.N wrote: >> >> When Node.js appear async/await, many developers and projects will >> migrate to a Node.js, if PHP is not implement async APIs. >> >> Hopefully, Dmitry Stogov

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

On Tue, Sep 29, 2015 at 8:24 PM, Rowan Collins wrote: > On 29 September 2015 16:22:30 BST, Thomas Hruska > wrote: >>On 9/29/2015 6:52 AM, Joe Watkins wrote: >>> We shouldn't reserve words on a whim ... >>> >>> async/await doesn't solve any

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

On 10/08/2015 04:14 PM, Larry Garfield wrote: On 10/01/2015 01:59 AM, Stephen Coakley wrote: So then, in summary, threads & multiprocessing enables you to do more *work* simultaneously, while async **maximizes the usefulness of each thread you have**. So using both is actually an incredibly

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

On 10/01/2015 01:59 AM, Stephen Coakley wrote: So then, in summary, threads & multiprocessing enables you to do more *work* simultaneously, while async **maximizes the usefulness of each thread you have**. So using both is actually an incredibly good thing, but they aren't the same nor

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

On 09/29/2015 10:22 AM, Thomas Hruska wrote: On 9/29/2015 6:52 AM, Joe Watkins wrote: We shouldn't reserve words on a whim ... async/await doesn't solve any problems for multithreaded programming, at all ... it solves problems for asynchronous programming, a different concept ... let's not

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

On 09/29/2015 01:04 PM, S.A.N wrote: Implementing elegant, readable, and stable asynchronous code in userland PHP code is very possible. In fact, I’ve done exactly this with Icicle (https://github.com/icicleio/icicle). Icicle uses generators and promises to implement coroutines. When a

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

Hi 2015-09-29 7:30 GMT+02:00 Pierre Joye : > 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

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

On Tue, 2015-09-29 at 08:49 +0200, Kalle Sommer Nielsen wrote: > Hi > > 2015-09-29 7:30 GMT+02:00 Pierre Joye : > > 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 > >

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

We shouldn't reserve words on a whim ... async/await doesn't solve any problems for multithreaded programming, at all ... it solves problems for asynchronous programming, a different concept ... let's not confuse the two ... As mentioned you don't need any special syntax or reserved words for

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

Sorry, that was all over the place ... was on way out the door ... What I should have said is that async/await don't directly solve problems, they are nice calling conventions for async APIs, but the APIs must exist before we talk about reserving or adding anything else. The real problem is that

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

On 9/29/2015 6:52 AM, Joe Watkins wrote: We shouldn't reserve words on a whim ... async/await doesn't solve any problems for multithreaded programming, at all ... it solves problems for asynchronous programming, a different concept ... let's not confuse the two ... Actually, it does.

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

Hi Thomas, > On Sep 29, 2015, at 10:22 AM, Thomas Hruska wrote: > > On 9/29/2015 6:52 AM, Joe Watkins wrote: >> We shouldn't reserve words on a whim ... >> >> async/await doesn't solve any problems for multithreaded programming, at >> all ... it solves problems for

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

Thomas, On Tue, Sep 29, 2015 at 11:22 AM, Thomas Hruska wrote: > On 9/29/2015 6:52 AM, Joe Watkins wrote: >> >> We shouldn't reserve words on a whim ... >> >> async/await doesn't solve any problems for multithreaded programming, at >> all ... it solves problems for

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

On Wed, Sep 30, 2015 at 1:16 AM, Sara Golemon wrote: > On Tue, Sep 29, 2015 at 3:00 PM, Dmitry Stogov wrote: > > 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

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

On Wed, Sep 30, 2015 at 1:22 AM, Johannes Schlüter wrote: > On Tue, 2015-09-29 at 11:29 -0700, Sara Golemon wrote: > > On Mon, Sep 28, 2015 at 10:30 PM, Pierre Joye > wrote: > > > This model totally failed for us in the past. And given that these >

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

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

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

On Tue, Sep 29, 2015 at 3:00 PM, Dmitry Stogov wrote: > 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

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

On Tue, 2015-09-29 at 11:29 -0700, Sara Golemon wrote: > On Mon, Sep 28, 2015 at 10:30 PM, Pierre Joye 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

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

On Tue, 2015-09-29 at 21:04 +0300, S.A.N wrote: > > When Node.js appear async/await, many developers and projects will > migrate to a Node.js, if PHP is not implement async APIs. > > Hopefully, Dmitry Stogov and others, will make another surprise: > PHP-Next-Async? :) My claim is that if you're

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

> Implementing elegant, readable, and stable asynchronous code in userland PHP > code is very possible. In fact, I’ve done exactly this with Icicle > (https://github.com/icicleio/icicle). Icicle uses generators and promises to > implement coroutines. When a coroutine yields a promise, the

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

On 29 September 2015 16:22:30 BST, Thomas Hruska wrote: >On 9/29/2015 6:52 AM, Joe Watkins wrote: >> We shouldn't reserve words on a whim ... >> >> async/await doesn't solve any problems for multithreaded programming, >at >> all ... it solves problems for asynchronous

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

On Mon, Sep 28, 2015 at 10:30 PM, Pierre Joye 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

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

On Sep 28, 2015 11:53 PM, "Levi Morrison" wrote: > > On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska wrote: > > On 9/28/2015 1:29 AM, S.A.N wrote: > >> > >> Are there any future plans for - async/await? > >> This need to know now, not to use these words to

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

On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska wrote: > On 9/28/2015 1:29 AM, S.A.N wrote: >> >> Are there any future plans for - async/await? >> This need to know now, not to use these words to constants, and class >> names... > > > async/await is the single greatest

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

Den 2015-09-28 kl. 18:53, skrev Levi Morrison: On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska wrote: On 9/28/2015 1:29 AM, S.A.N wrote: Are there any future plans for - async/await? This need to know now, not to use these words to constants, and class names...

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

On 9/28/2015 1:29 AM, S.A.N wrote: Are there any future plans for - async/await? This need to know now, not to use these words to constants, and class names... async/await is the single greatest addition to modern application development in the last 20 years. Every language needs these

[PHP-DEV] async/await - is future reserved words in PHP 7.x?

Are there any future plans for - async/await? This need to know now, not to use these words to constants, and class names... -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

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

Hello, > On Sep 28, 2015, at 3:29 AM, S.A.N wrote: > > Are there any future plans for - async/await? > This need to know now, not to use these words to constants, and class names... > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: