Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106324
Message-ID: <B3A5DE4D-0BCE-4252-8609-6380610C3C0A@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_07486AFF-0ED3-49FB-B6C4-FAC95FBD5F37"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 29 Jul 2019 17:36:15 +0200
In-Reply-To: <CAF+90c-=9HjQHMeTeb5sggKMhtZFGoC7f0766dVavAtpVxLUDg@mail.gmail.com>
Cc: Rowan Collins <rowan.collins@gmail.com>,
 PHP Internals List <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <CAF+90c87_Zd07ftVe29=GdjxhxjkFG+VXfm_ZZ3QWqER50QLuA@mail.gmail.com>
 <CAF+90c8hTaL56MQDu6=8+A2iGf9T3kxhj9TMtZdmvwNNROJO3w@mail.gmail.com>
 <CALKiJKoEmeLmf_H4sSUZ3brdqUgtHQH+6V0WAXe-OuPG5zNc5w@mail.gmail.com>
 <CAF+90c8a_CWVyVfnt3so_u-0Df5zxwRX1=ASp=BXcOtGggeANg@mail.gmail.com>
 <9aba78c9-f04d-45b8-6c34-ad1c2472ef76@gmail.com>
 <CADyq6sLrDh4ORdmJ4n9qKmhWjHvOzgvHhQ0PXYnDxS6SBUq6Eg@mail.gmail.com>
 <75d04139-b944-f204-f988-959fa6f3e305@gmail.com>
 <CADyq6sLismPxQ5-aztMh35UfOXRAfHTX3imcT04KxEHedJx7iw@mail.gmail.com>
 <8CD3B476-ABF9-4DB7-96D3-217064023854@gmail.com>
 <CAF+90c-=9HjQHMeTeb5sggKMhtZFGoC7f0766dVavAtpVxLUDg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_07486AFF-0ED3-49FB-B6C4-FAC95FBD5F37
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 29 juil. 2019 =C3=A0 16:40, Nikita Popov <nikita.ppv@gmail.com> a =
=C3=A9crit :
>=20
>=20
> You seem to be agreeing with what I originally said: That by-reference =
passing is mainly useful to interoperate with by-reference internal =
functions, which don't exactly leave you with a choice.
>=20

To be clear: No, I=E2=80=99m not agreeing with: =E2=80=9CThat =
by-reference passing is mainly useful to interoperate with by-reference =
internal functions=E2=80=9D. I don=E2=80=99t think that every PHP =
developer consider that the design of `array_push()` and =
`array_multisort()` is flawed, and that they must avoid such a pattern =
in their own user-defined functions.

More generally, I don=E2=80=99t think that every PHP developer consider =
that only the latest trendy coding style is valid, or that every legacy =
code not following that style should be rewritten.

=E2=80=94Claude


--Apple-Mail=_07486AFF-0ED3-49FB-B6C4-FAC95FBD5F37--