Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88916 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90497 invoked from network); 22 Oct 2015 01:12:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2015 01:12:47 -0000 Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.212.177 mail-wi0-f177.google.com Received: from [209.85.212.177] ([209.85.212.177:36534] helo=mail-wi0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 68/A4-55035-E0838265 for ; Wed, 21 Oct 2015 21:12:46 -0400 Received: by wicfx6 with SMTP id fx6so114567314wic.1 for ; Wed, 21 Oct 2015 18:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=M39Cv6sN79jPYFGnHgIix2X1A9hOWY+x5k+rhdJkhvw=; b=pKenFX7Cb64foAwtmgIhc9Ug9RA6aI+PA5HdMj1RTVAevipm4H3aYRwFbIqLqbrNkk 8vZEA677QPjpKSrPl6bWydvRrZlusAlWCWX2hfspNQnnp+aYRVek7OwzPX/0oGYlb5xM J8dY1nqIYmr5VqkMgG5wSZurUhuJnwK2GRBr+p0qq8g++/Nq48x9jaQlWKOi2429VqTx 9VPa/M52aJwJGsNOmnvZ9DmlZkAeOvpkFyuLGVJH5KitfB8W4XE0n8gRBqIe5eKHB0sz VsKCzhnv8F5t8ewy6VvmGyzH9rBLIMV8k15FdujM+K1yi3hGcj2fWooGn3+BWAS3bxO3 fHvw== X-Received: by 10.180.23.161 with SMTP id n1mr13934117wif.53.1445476363355; Wed, 21 Oct 2015 18:12:43 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.194.7.105 with HTTP; Wed, 21 Oct 2015 18:12:03 -0700 (PDT) In-Reply-To: <1443564482.10840.7.camel@kuechenschabe> References: <56095A0C.4070306@cubiclesoft.com> <1443529244.15520.67.camel@kuechenschabe> <560AACB6.9080909@cubiclesoft.com> <09A2B2D4-EAE9-46E8-AF5C-4E83C4F3D8A2@icicle.io> <1443564482.10840.7.camel@kuechenschabe> Date: Thu, 22 Oct 2015 03:12:03 +0200 X-Google-Sender-Auth: 9bBNfMNRxzfw2EjPWlnm1jbquDE Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: "S.A.N" , Aaron Piotrowski , Thomas Hruska , Joe Watkins , Kalle Sommer Nielsen , Pierre Joye , Levi Morrison , PHP internals 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 Wed, Sep 30, 2015 at 12:08 AM, Johannes Schl=C3=BCter 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 and others, will make another surprise: >> PHP-Next-Async? :) > > My claim is that if you're doing something CPU-intensive which can be > parallelized in PHP you're most likely doing something wrong but you > should send this to a processing service. PHP imo needs a stronger > async-IO story. > > Node.js is a completely different thing and people don't switch because > it has a async feature, but people pick it (aside from hype) since it > solves different issues. > > Anyways. This is irrelevant for *this* thread. This thread was about > reserving async/await keywords. The discussion has proven that there is > no clear plan. Therefore we should not reserve any keywords. Yep I also agree with that, we should reserve when we are sure (voted RFC) keywords will be used. Julien.P