Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106331
To: Stephen Reay <php-lists@koalephant.com>,
 Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
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>
 <CALKiJKrs1Gae9h5X03yJrPckP5uZp6w_EWAEBbmY1Ka_1++wXg@mail.gmail.com>
 <95E55BC4-1E0F-4FAA-B565-C4D20C054219@koalephant.com>
 <e566b063-a29c-1786-9556-9514e563c20f@telia.com>
Message-ID: <4b225996-29df-97a9-62d0-104f3ec36e29@telia.com>
Date: Tue, 30 Jul 2019 00:47:14 +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: <e566b063-a29c-1786-9556-9514e563c20f@telia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
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-30 kl. 00:27, skrev Björn Larsson:

> Den 2019-07-29 kl. 20:00, skrev Stephen Reay:
>>> On 29 Jul 2019, at 22:34, Rowan Collins <rowan.collins@gmail.com> 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
>
PS I meant "replace current PHP way of handling reference parameters".