Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109018
To: internals@lists.php.net
References: <CAFLRTJ99i_mjHd9umq77DOi4DdnF_-8Gv7k6zVqE_J0S-8ps5w@mail.gmail.com>
 <CAFPFaML2RvOm+WwhddavyVoM5VGC=ghzcVPh4nXuRiO7tqe6uA@mail.gmail.com>
 <E1047632-35F7-493E-B80A-35AEF30E89AA@newclarity.net>
Message-ID: <46536651-3d34-11fc-db21-f3cccbbf9b3d@gmail.com>
Date: Sat, 14 Mar 2020 19:13:58 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <E1047632-35F7-493E-B80A-35AEF30E89AA@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Associated Arrays as function parameters
From: rowan.collins@gmail.com (Rowan Tommins)

On 14/03/2020 15:57, Mike Schinkel wrote:
>> What you are looking for are Named Parameters, there have been multiple
>> RFCs about which have all been more or less abandoned from what I see.
>> https://wiki.php.net/rfc/namedparameters  (From 2012)
>> https://wiki.php.net/rfc/named_params  (From 2013)
>> https://wiki.php.net/rfc/simplified_named_params  (From 2016)
> Can anyone summarize why these did not move forward?


Without digging back into the archives, my memory is that points of 
discussion included:

- The choice of syntax.

- Support for internal functions, which don't declare parameters in the 
same way. I believe this is now solved, or at least vastly improved, by 
providing reflection information for internal functions via PHP-syntax 
stubs (see https://externals.io/message/105851 and 
https://externals.io/message/105970).

- Handling of inheritance: what happens if a class overrides a base 
method (or implements an interface method) but uses different parameter 
names? If all parameters are immediately accessible by name (i.e. no 
extra opt-in is needed in the definition), there will be a large amount 
of existing code which would immediately break LSP this way.

- Mixing named and positional parameters in a single function call.

- Handling of variadics, both the function foo(...$args) syntax and the 
special func_get_args() etc functions

- Behaviour when a non-optional parameter is skipped (all three RFCs 
predate https://wiki.php.net/rfc/too_few_args)


Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]