Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88915
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.176 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <A3C8DE36-3EDF-4C5E-A26E-6EA2B3BF0CC9@gmail.com>
References: <CALW=WEBPC2N2tzmU1uB_v93YXLa1MA97=0_q7zP0F6G+uRPDNQ@mail.gmail.com>
 <56095A0C.4070306@cubiclesoft.com> <CAFMT4NqaqVX-KHh9iz_R05wxp2h=aajv5RuQGh2EQVSNHoLGaQ@mail.gmail.com>
 <CAEZPtU6cgVrqh0PNYybcrk4_X36m5K=dp280G=7OfzjYBzxJpQ@mail.gmail.com>
 <CAJW__o2727mc+ugUd2NvvYTB-r0dC68dkUOke+oPjwZDtZA+vQ@mail.gmail.com>
 <1443529244.15520.67.camel@kuechenschabe> <CAL=_i_kXeBiQ4O9u-0mXu47zKt2-c9uQSWGZ4KReTfjzbzT7kw@mail.gmail.com>
 <560AACB6.9080909@cubiclesoft.com> <A3C8DE36-3EDF-4C5E-A26E-6EA2B3BF0CC9@gmail.com>
Date: Thu, 22 Oct 2015 03:10:50 +0200
Message-ID: <CAMUwpuQxtR6sZ2rKpECa2EAPN+Zq4OwWbnt1duiOWYv2cRCb4A@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] async/await - is future reserved words in PHP 7.x?
From: jpauli@php.net (Julien Pauli)

On Tue, Sep 29, 2015 at 8:24 PM, Rowan Collins <rowan.collins@gmail.com> wr=
ote:
> On 29 September 2015 16:22:30 BST, Thomas Hruska <thruska@cubiclesoft.com=
> 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 confuse the two ...
>>
>>Actually, it does.  Asynchronous and multithreaded programming are
>>attempts at solving the exact same problem:  Simultaneously handling
>>multiple data streams in whatever form that takes whether that be
>>network, hard drive, random device XYZ, RAM, or even CPU.  The former
>>says, "Let's wait until we can read or write and continue when we have
>>data."  The latter says, "Let's read and write but let the OS handle
>>context switching to give the appearance of simultaneously handling
>>multiple data streams."
>
> That description may have held a few years ago, when processes and thread=
s were nearly always time-slices on a single CPU core, but surely on a mode=
rn system there can be real simultaneity, because even the cheapest  laptop=
 has multiple CPU cores. An asynchronous approach is useful for cases of "d=
o something else while I wait for this background task to complete", but se=
ems less so for "do both of these things actively, using whatever resource =
is available".
>
> It may be that the first class of problem is more common, but that doesn'=
t make the two equivalent.

Remember that discussion we had some years ago ? ;-)

Async IOs etc...  some parts can still be found on the wiki
(https://wiki.php.net/ideas/php6/engine).

I hope we'll be able to collaborate about this subject for a PHP-Next,
like PHP 8.


Julien.P