Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93366
Return-Path: <pierre.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 77253 invoked from network); 17 May 2016 09:08:09 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 17 May 2016 09:08:09 -0000
Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.46 as permitted sender)
X-PHP-List-Original-Sender: pierre.php@gmail.com
X-Host-Fingerprint: 209.85.218.46 mail-oi0-f46.google.com  
Received: from [209.85.218.46] ([209.85.218.46:33366] helo=mail-oi0-f46.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D0/B1-57067-87FDA375 for <internals@lists.php.net>; Tue, 17 May 2016 05:08:08 -0400
Received: by mail-oi0-f46.google.com with SMTP id v145so14990994oie.0
        for <internals@lists.php.net>; Tue, 17 May 2016 02:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc;
        bh=OfAOyJ4X2sCaYU5/34kqgcYd5AtNeYJbUEYly9Ipgx8=;
        b=sXsu8HiC1zaMdwakdG25nitYjLAoqEH4WjJ95Fk7L/nhYNr1kakeEZIPaJcMXGDDb1
         NyQ+AWemgoh0CkMjUYWIGCQxdPvzkAM4OmOszYxWM8BkbCNifyi82zQBlOn9wsAnusvb
         vmOfOiF+lOt8dK9KuFAFXMv8Rtu0Sb3MTdZKh/e5XmRIoMZ4Fw+YSxBTTSN6jsjdO9n8
         Xo12AqA+etPtiSmFg5/klx1I9uEv7QhkPjledoZsV0AN/Env3T/ZuFoFRGYlxLYx+Dl/
         AtIGorewsEFKkOdY8mXuX3B+SR3It6lfEknioOJEr6KYUnw2oNYHr5TXK4pvx3ws3FWw
         gnLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:cc;
        bh=OfAOyJ4X2sCaYU5/34kqgcYd5AtNeYJbUEYly9Ipgx8=;
        b=H8x8mK7puCBXC9+yk8LTw2bnfIvdTDbbyjQyO44bdmEfnUy4O/uVbCiANacc2VLaIq
         3MWWLEFg1CP9i8wGv02HwRBooSKI/0l0BUyi7VKFG21tbhly97tmYbvUHwA378QQ3Yn2
         kp42w7SdbMEwJvQVJtmO8Atwu2VUuF1i2dr1j6vcNINN1BOOEetgiVCDj/MnQizZpqoe
         XsxScAgMe8Mvhm9c0NAWRYH4KJN3o4esMF280sfy+HfwmHXx1lcdDxY5Ffx1xjBIQs4H
         DfnVkR1JLHflkaom2rCHro4n9jtWVEqB3lANCXRjEMLkoNyrfYkLRcN5aCKHBZIUROxP
         /Hmw==
X-Gm-Message-State: AOPr4FXkSHsXSe43DCsdunaw3Oei5uot1gxOvONGWoYCGWrHyZuMt7Q/DAlqYEhLdpK7KYT26Z2ztRQPaeDy3Q==
MIME-Version: 1.0
X-Received: by 10.202.217.67 with SMTP id q64mr63178oig.151.1463476085704;
 Tue, 17 May 2016 02:08:05 -0700 (PDT)
Received: by 10.202.215.193 with HTTP; Tue, 17 May 2016 02:08:03 -0700 (PDT)
Received: by 10.202.215.193 with HTTP; Tue, 17 May 2016 02:08:03 -0700 (PDT)
In-Reply-To: <CAESVnVpa5j=fagr-wm5+DzKKX=wzTN1p8+Kv3-KtGpuyH51b0A@mail.gmail.com>
References: <CAESVnVpa5j=fagr-wm5+DzKKX=wzTN1p8+Kv3-KtGpuyH51b0A@mail.gmail.com>
Date: Tue, 17 May 2016 16:08:03 +0700
Message-ID: <CAEZPtU5mOcpYqzSiyMcn9hjqL0YKSQwcFAT8LMfo_mHyZX6HWA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113cf48c39cf6a053306141a
Subject: Re: [PHP-DEV] [RFC] Pipe Operator
From: pierre.php@gmail.com (Pierre Joye)

--001a113cf48c39cf6a053306141a
Content-Type: text/plain; charset=UTF-8

Hi Sara,

On Apr 30, 2016 3:11 AM, "Sara Golemon" <pollita@php.net> wrote:
>
> This is one of my favorites out of HackLang.  It's pure syntactic
> sugar, but it goes a long way towards improving readability.
> https://wiki.php.net/rfc/pipe-operator

After I first read the rfc my immediate feeling was negative. Yet another
syntaxic sugar that will be used so rarely that I will have to try&fail and
rtfm when I see it.

The cases presented in this thread and in other discussions changed my
mind. I will vote for it.

Thanks
Pierre

--001a113cf48c39cf6a053306141a--