Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93274
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.110.113 as permitted sender)
To: Quim Calpe <quim@kalpe.com>
CC: "davey@php.net" <davey@php.net>, Larry Garfield <larry@garfieldtech.com>,
	"internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] Pipe Operator
Thread-Index: AQHRolNOHPYtov7fr0u1QLMw6YCXeZ+jJ1UAgANBmQCAACBagIAA5DwAgAAcmICAAAaoAIAAAp+AgAAB6YCAAAFcgIAACKgAgAAPBICAAAOdgIAADYmAgAeDeoCAAKavAIAAO4oAgAAN4wCAAAURAIAAppQAgACq0ACAAAgDAIAC4RKAgAC8HICAACG0gIAABA5S
Date: Thu, 12 May 2016 12:48:19 +0000
Message-ID: <92E7F8A8-0845-48A7-91B1-9554C5F66C9D@zend.com>
References: <CAESVnVpa5j=fagr-wm5+DzKKX=wzTN1p8+Kv3-KtGpuyH51b0A@mail.gmail.com>
 <39071a01-a42c-0952-b3a8-b4769c79b56b@fleshgrinder.com>
 <CAESVnVpwbYdeENZ4CW1m8KiLSZv87x5TO3+72uYYR262rgYL3Q@mail.gmail.com>
 <0ac3be89-6fb4-610a-ef89-0928f264f96c@fleshgrinder.com>
 <CAESVnVpBn2fpK-BQXj2261mTMG7ZUK1XwOS6jZn1wiYBEs61mg@mail.gmail.com>
 <71379db5-b7b8-78b3-ada5-eee34e6e22d6@fleshgrinder.com>
 <CAObuZdtS-gn3gT6L2bwshF4H9KzxZSaCsu41CYtyeT+=SOCSyg@mail.gmail.com>
 <a25612f2-fb09-c25e-ca30-daf850acaa96@fleshgrinder.com>
 <CAObuZduo2-mnZMbgKFEWN1=yxqgqh_8RCN7GSpCTYCNXVjWJ_w@mail.gmail.com>
 <fe837e8b-2a6e-516e-33f0-cfcca172d565@fleshgrinder.com>
 <CAGa2bXaKWu+WJ7unZ2TfG03KUYY3JyNG=FK3cUbR3PL244znyA@mail.gmail.com>
 <ddcfc338-a2fb-a06f-36ef-30e105772779@gmail.com>
 <CAESVnVr07J9UF3Dh7a1rMudMmQjeYuayvoT8Rmde+rfCBK6vnQ@mail.gmail.com>
 <452ddb93-1f47-1d0f-4f24-bedbff506b27@gmail.com>
 <CAESVnVqohR7rkaJASZ0rFuAD6GEiasqbAak-fJB3+K2vSKqHFQ@mail.gmail.com>
 <98.61.11104.A1D41375@pb1.pair.com>
 <7c94ca37-e188-dd2b-a66f-bb63bf03041a@gmail.com>
 <1463008795.1856219.605250569.74618FC4@webmail.messagingengine.com>
 <CANaX5nekRmhNKmY78tHRrev0_B3a-faRsQ8Jf=yA-jCkEP5-Ew@mail.gmail.com>,<CAKrrN64bu+T0Sv4V6mo7i1cRYAh1W8Kx8tQ_rqQmZagXBTqKuQ@mail.gmail.com>
In-Reply-To: <CAKrrN64bu+T0Sv4V6mo7i1cRYAh1W8Kx8tQ_rqQmZagXBTqKuQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-8-i"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 May 2016 12:48:19.3793
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR02MB298
Subject: Re: [PHP-DEV] [RFC] Pipe Operator
From: zeev@zend.com (Zeev Suraski)


> On 12 =E1=EE=E0=E9 2016, at 15:34, Quim Calpe <quim@kalpe.com> wrote:
>=20
>> On Thu, May 12, 2016 at 12:33 PM, Davey Shafik <davey@php.net> wrote:
>>=20
>> On Thu, May 12, 2016 at 1:19 AM, Larry Garfield <larry@garfieldtech.com>
>> wrote:
>>=20
>>>> On Mon, May 9, 2016, at 10:21 PM, Stanislav Malyshev wrote:
>>>> Hi!
>>>>=20
>>>>> |> seems like a common symbol to use, but it admittedly does look a
>>>>=20
>>>> So, usage in one semi-obscure language (F#) and one completely obscure
>>>> one (Elixir) - Clojure doesn't use |> - and one proposal for Javascrip=
t
>>>> now qualifies for "common". And that counting the fact that neither of
>>>> them actually uses the worst part of proposed syntax - magic variable
>> $$.
>=20
> Is $0 being considered? It's not ideal but is used as "pattern match
> reference" in preg_replace, so we have a (sort of) precedent here. Same f=
or
> $1 (first capturing subpattern).
>=20

Folks,

Whether it's $$ or !# or $0 or any other random symbol doesn't really matte=
r.  What matters is the introduction of a new symbol for this purpose and t=
he non intuitive nature it will have.

This is not analogous to the namespace operator, where it was obvious we wa=
nted namespaces, and was only a matter of picking the right one.  It's also=
 not analogous in the sense that codebases that use namespaces tend to use =
them all over, so the likelihood of not being acquainted with it is slim.

Here we have a completely optional syntactic sugar, that's not nearly as wi=
dely useful as OOP or namespaces, and the question is whether the added com=
plexity of a new operator, a new symbol and the new semantics around them b=
oth are worth the benefit of introducing them.  IMHO it's not.

Zeev=