Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108715
Date: Fri, 21 Feb 2020 22:20:21 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAF+90c-Lx2dddeXGw9Ce4xbVwJ49oKu-xzNJ1TRN4HYn6_eZ4w@mail.gmail.com>
References: <CAF+90c-Lx2dddeXGw9Ce4xbVwJ49oKu-xzNJ1TRN4HYn6_eZ4w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: PHP internals <internals@lists.php.net>
Message-ID: <8B2AFC37-9425-440C-B89D-61CBAAB0CDDD@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Explicit call-site pass-by-reference (again)
From: rowan.collins@gmail.com (Rowan Tommins)

On 20 February 2020 14:13:58 GMT+00:00, Nikita Popov <nikita=2Eppv@gmail=2E=
com> wrote:
>Hi internals,
>
>I'd like to start the discussion on the "explicit call-site
>pass-by-reference" RFC again:
>https://wiki=2Ephp=2Enet/rfc/explicit_send_by_ref


Hi Nikita,

Thanks for putting the case for this so clearly=2E My instinctive reaction=
 is still one of frustration that the pain of removing call-site ampersands=
 was in vain, and I will now be asked to put most of them back in=2E It's a=
lso relevant that users already find where & should and should not be used =
very confusing=2E There is a potential "PR" cost of this change that should=
 be weighed against the advantages=2E

I'm also not very keen on internal functions being able to do things that =
can't be replicated on userland, and this RFC adds two: additional behaviou=
r for existing "prefer-ref" arguments, and new "prefer-value" arguments=2E

My current opinion is that I'd rather wait for the details of out and inou=
t parameters to be worked out, and reap higher gains for the same cost=2E F=
or instance, if preg_match could mark $matches as "out", I'd be more happy =
to run in a mode where I needed to add a call-site keyword=2E

Regards,

--=20
Rowan Tommins
[IMSoP]