Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105128
Message-ID: <96516724-154F-4C5E-B69D-F5C978D600A0@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DC9D0944-97B1-43A1-A1F5-11E24A1309F7"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Sun, 7 Apr 2019 12:21:35 +0200
In-Reply-To: <CAHE1EdtPNozp_ZWNf07Y5HqDE00_+L3z0BFcRW2U0qfjX3_SVA@mail.gmail.com>
Cc: Internals <internals@lists.php.net>
To: Craig Duncan <php@duncanc.co.uk>
References: <CAHE1EdtbMsGy-TSJNvrHYcUKq=KamekJOd1+9AOV4ME2VB1j+w@mail.gmail.com>
 <169f6751c80.27c1.08be835b7d1a2c2edb4c4286afe1a236@gmail.com>
 <CAHE1EdtPNozp_ZWNf07Y5HqDE00_+L3z0BFcRW2U0qfjX3_SVA@mail.gmail.com>
Subject: Re: [PHP-DEV] Parameter skipping
From: gadelat@gmail.com (Gabriel O)

--Apple-Mail=_DC9D0944-97B1-43A1-A1F5-11E24A1309F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I mean it=E2=80=99s easier than named parameters. I guess I replied to =
wrong thread, but wanted to contrast =E2=80=9Cdefault=E2=80=9D with =
JSON_DEFAULT_DEPTH. Accepting string in integer parameter just creates =
mores issues. And please don=E2=80=99t use name conflicts as argument =
for not adding something. It=E2=80=99s absurd to stop adding anything in =
minor releases because name can conflict with userland, especially in =
case name is prefixed like here.

> On 7. Apr 2019, at 11:31, Craig Duncan <php@duncanc.co.uk> wrote:
>=20
> Hi Gabriel, do you mean a constant for every parameter's default =
value? I'm not sure how that's easier, and it's technically worse for BC =
as *default* is already a keyword but your new global constants could =
clash with userland ones.
>=20
>=20
>=20
> On Sun, 7 Apr 2019, 07:33 Gabriel O, <gadelat@gmail.com =
<mailto:gadelat@gmail.com>> wrote:
> Wouldn't better (and still easy and bc) solution be to just have =
constant=20
> holding default value?
>=20
> On 6 April 2019 11:16:02 PM Craig Duncan <php@duncanc.co.uk =
<mailto:php@duncanc.co.uk>> wrote:
>=20
> > Hi all,
> >
> > After starting to use https://wiki.php.net/rfc/json_throw_on_error =
<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 =
<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
>=20
>=20
>=20


--Apple-Mail=_DC9D0944-97B1-43A1-A1F5-11E24A1309F7--