Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93127
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.215.41 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <452ddb93-1f47-1d0f-4f24-bedbff506b27@gmail.com>
References: <CAESVnVpa5j=fagr-wm5+DzKKX=wzTN1p8+Kv3-KtGpuyH51b0A@mail.gmail.com>
	<bb8bdb06-b9e5-7e02-3aa5-d54121b8eacb@fleshgrinder.com>
	<CAESVnVpFCN-cC1pyiZ+ApOneUagb9ncUfOHqhNtE+WQaBkH_TA@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>
Date: Mon, 9 May 2016 09:41:48 -0700
Message-ID: <CAESVnVqohR7rkaJASZ0rFuAD6GEiasqbAak-fJB3+K2vSKqHFQ@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Pipe Operator
From: pollita@php.net (Sara Golemon)

On Sun, May 8, 2016 at 11:45 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>> Yep, that's exactly what "->" does.  It's just pointless syntactic
>
> No, not really. Calling method on an object is an universally accepted
> phrase in many languages.
>
I never said it wasn't.  I said it was pointless syntactic sugar.

> Moreover, there's no easy and more readable way to call methods in PHP,
> so -> is the best way to go.
>
But there are ways to implement "oop" with explicit data passage.
Ways which could have been leveraged in PHP3.  We don't use those ways
because it's a PITA and produces unreadable code.  Which is what
syntactic sugar is meant to alleviate.

> Moreover, calling methods is a very frequent operation, and any time you
> need it, regardless of what is the circumstance, you'd use ->
>
Calling functions, chaining the output of one into the next is also a
frequent argument.

> Neither of these is true for |>-$$ thing - it does not have any matches
> in any languages I can think of.
>
You lack imagination.  Here's three to get you started:

Elixir: http://elixir-lang.org/getting-started/enumerables-and-streams.html#the-pipe-operator
F#: https://msdn.microsoft.com/en-us/library/dd233229.aspx#Anchor_11
Clojure: https://clojuredocs.org/clojure.core/-%3E

And if they seem to obscure, how about this proposal for Javascript?
https://github.com/mindeavor/es-pipeline-operator


>> Oh, sorry, we were talking about the function version of ->, my
>> mistake.  That's a totally different thing.
>
> I'm sorry I didn't get what you meant here. "function version of ->"
> makes no sense to me - function version of -> is the function call itself.
>
$foo->bar() calls the bar() method invisibly passing $foo as its
similarly hidden $this argument.
$foo |> bar($$) calls the bar() method quite visible passing $foo as
its explicitly non-hidden first argument.

The pipe call is clear and easily traces, the object call requires
understanding OOP.  I'll grant that OOP is much more common, and
therefore generally understood by individuals who already know OOP (as
tautologous as that statement is).

-Sara