Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105129
Date: Sun, 07 Apr 2019 11:26:04 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <00ab01d4ecfe$e0b03680$a210a380$@jhdxr.com>
References: <CAHE1EdtbMsGy-TSJNvrHYcUKq=KamekJOd1+9AOV4ME2VB1j+w@mail.gmail.com> <CALGLHq189gZfSu0m-5D6VbcS5_ABkWi2sKjRE5ZQpfyFScOsDw@mail.gmail.com> <a544f63e-946f-1cfd-8411-9b4a0d36b18f@gmail.com> <00ab01d4ecfe$e0b03680$a210a380$@jhdxr.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <CBDB7A0E-A971-4B6F-A66E-950BA4F0DFD4@gmail.com>
Subject: RE: [PHP-DEV] Parameter skipping
From: rowan.collins@gmail.com (Rowan Collins)

On 7 April 2019 06:00:53 BST, CHU Zhaowei <me@jhdxr=2Ecom> wrote:
>The [named parameters](https://wiki=2Ephp=2Enet/rfc/named_params) was
>proposed in 2013=2E Does the problems which stopped us before still exist
>in 2019? Since we all agree named parameter should be a better
>solution, why not take a look at it first?

I'm not 100% convinced named parameters are the solution to this problem, =
in all cases=2E

In order to use named parameters, somebody needs to have declared what tho=
se names are, and made them a stable API=2E If they're automatically suppor=
ted on existing functions, the author might not intend them to be used, or =
even realise they can, so not keep them stable (I tend to think of paramete=
r names as local, not contractual)=2E

To use a default-skipping keyword, you need no extra promise than that alr=
eady made, namely that the default for any parameter is a valid value for t=
hat parameter=2E

Regards,

--=20
Rowan Collins
[IMSoP]