Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106325 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 82051 invoked from network); 29 Jul 2019 20:36:09 -0000 Received: from unknown (HELO mail1.25mail.st) (206.123.115.54) by pb1.pair.com with SMTP; 29 Jul 2019 20:36:09 -0000 Received: from [10.0.1.62] (unknown [49.48.243.173]) by mail1.25mail.st (Postfix) with ESMTPSA id AA5BE604CA; Mon, 29 Jul 2019 18:00:45 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (16F203) In-Reply-To: Date: Tue, 30 Jul 2019 01:00:35 +0700 Cc: PHP Internals List Content-Transfer-Encoding: quoted-printable Message-ID: <95E55BC4-1E0F-4FAA-B565-C4D20C054219@koalephant.com> References: <9aba78c9-f04d-45b8-6c34-ad1c2472ef76@gmail.com> <75d04139-b944-f204-f988-959fa6f3e305@gmail.com> <8CD3B476-ABF9-4DB7-96D3-217064023854@gmail.com> To: Rowan Collins Subject: Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax From: php-lists@koalephant.com (Stephen Reay) > On 29 Jul 2019, at 22:34, Rowan Collins wrote: >=20 > I guess what I had in mind was that *in the long-term*, > out/inout parameters would replace & parameters, Excuse my ignorance (presumably about the complexity involved) if this is ob= vious, but if out/inout parameters are considered to be a better solution fo= r the problem references generally solve (I don=E2=80=99t doubt that they ar= e, even as a user of references), why is that inherently a =E2=80=9Clong ter= m=E2=80=9D goal? Is it not a feasible goal for next years release? Cheers Stephen=20=