Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106329 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29937 invoked from network); 30 Jul 2019 01:02:19 -0000 Received: from unknown (HELO v-smtpout1.han.skanova.net) (81.236.60.154) by pb1.pair.com with SMTP; 30 Jul 2019 01:02:19 -0000 Received: from [192.168.7.8] ([213.64.245.126]) by cmsmtp with ESMTPA id sE6ghxBGHpIpGsE6ghvAWi; Tue, 30 Jul 2019 00:27:03 +0200 To: Stephen Reay , Rowan Collins Cc: PHP Internals List References: <9aba78c9-f04d-45b8-6c34-ad1c2472ef76@gmail.com> <75d04139-b944-f204-f988-959fa6f3e305@gmail.com> <8CD3B476-ABF9-4DB7-96D3-217064023854@gmail.com> <95E55BC4-1E0F-4FAA-B565-C4D20C054219@koalephant.com> Message-ID: Date: Tue, 30 Jul 2019 00:27:09 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <95E55BC4-1E0F-4FAA-B565-C4D20C054219@koalephant.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-CMAE-Envelope: MS4wfKK3RJe4Uo3lrIY+bSQ88WVTO99kc4mY5dcYNmNYc8R8mZ/oA1chTRNW4JE3NtL29P6v0s6G+M8jbyo3KqhOD2Vu0UXIrSQE1HlhBQcM1PRGTUJ12/WC 8fDGVT6+OFLNYJ3HtpwO9a0Cb+MTGN7QtOnqm3gXdHFhBkaFrJ4DsLt3UtGQStEE44rbpUmzd7KrpBBHK1j3LfwKIYRYFs8QOwsKiuOyiOq/ia0pmlhLcMos 92AS6PjO/GyvfTXr1StlrA== Subject: Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2019-07-29 kl. 20:00, skrev Stephen Reay: >> On 29 Jul 2019, at 22:34, Rowan Collins wrote: >> >> 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 obvious, but if out/inout parameters are considered to be a better solution for the problem references generally solve (I don’t doubt that they are, even as a user of references), why is that inherently a “long term” goal? Is it not a feasible goal for next years release? > > Cheers > Stephen To replace current PHP way of handling parameters is for sure a long-term goal, just imagine the BC break... To introduce out/inout parameters without phasing out references is probably a shorter goal to accomplish. r//Björn L