Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105123
MIME-Version: 1.0
Date: Sat, 6 Apr 2019 22:15:39 +0100
Message-ID: <CAHE1EdtbMsGy-TSJNvrHYcUKq=KamekJOd1+9AOV4ME2VB1j+w@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009ba36e0585e31bcc"
Subject: Parameter skipping
From: php@duncanc.co.uk (Craig Duncan)

--0000000000009ba36e0585e31bcc
Content-Type: text/plain; charset="UTF-8"

Hi all,

After starting to use https://wiki.php.net/rfc/json_throw_on_error in PHP
7.3 I've encountered the annoying issue of having to pass the $depth
parameter as 512 every time I want json_decode() to throw.

After doing this a few times I remembered the parameter skipping RFC that
Stas proposed a few years ago: https://wiki.php.net/rfc/skipparams

I've re-read the previous discussion and it seems to me there were two
common arguments against:
* Just design better APIs
* Named parameters would be better

Nobody has been able to crack named parameters (and it doesn't seem likely
anytime soon), and as we've seen from the JSON example above it's not
always as simple as having better APIs, so I wanted to see whether people
would be willing to support the *default* keyword for optional parameters
now.

Thanks,
Craig

--0000000000009ba36e0585e31bcc--