Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88543
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.160.172 cause and error)
MIME-Version: 1.0
In-Reply-To: <1443529244.15520.67.camel@kuechenschabe>
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>
Date: Tue, 29 Sep 2015 14:52:45 +0100
Message-ID: <CAL=_i_kXeBiQ4O9u-0mXu47zKt2-c9uQSWGZ4KReTfjzbzT7kw@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Kalle Sommer Nielsen <kalle@php.net>, Pierre Joye <pierre.php@gmail.com>, Levi Morrison <levim@php.net>, 
	PHP internals <internals@lists.php.net>, Thomas Hruska <thruska@cubiclesoft.com>, 
	"S.A.N" <ua.san.alex@gmail.com>
Content-Type: multipart/alternative; boundary=001a11472e22e635160520e320b4
Subject: Re: [PHP-DEV] async/await - is future reserved words in PHP 7.x?
From: pthreads@pthreads.org (Joe Watkins)

--001a11472e22e635160520e320b4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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
asynchronous execution, these problems are not solved by adding two words
to the parser. The API's might not be very nice, and there aren't enough of
them, but there is absolutely nothing stopping you writing asynchronous
code, and there wasn't in PHP4 either ...

Cheers
Joe

On Tue, Sep 29, 2015 at 1:20 PM, Johannes Schl=C3=BCter <johannes@schlueter=
s.de>
wrote:

> 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
>

--001a11472e22e635160520e320b4--