Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130295
Content-Type: text/plain;
	charset=utf-8
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Subject: Re: [PHP-DEV] [RFC] Display Function Arguments in Errors
In-Reply-To: <6c498ed3-3cb0-47a5-a64e-4ad202eba141@bastelstu.be>
Date: Thu, 12 Mar 2026 12:53:51 -0300
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <6EE06F93-E9F2-455E-B530-B2BF6FB4B648@cmpct.info>
References: <939CFA28-A6FF-433F-85A0-B83345CEF4A6@cmpct.info>
 <6c498ed3-3cb0-47a5-a64e-4ad202eba141@bastelstu.be>
To: =?utf-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
From: calvin@cmpct.info (Calvin Buckley)

On Mar 11, 2026, at 3:35=E2=80=AFPM, Tim D=C3=BCsterhus =
<tim@bastelstu.be> wrote:
>=20
> Hi
>=20
> On 3/11/26 16:55, Calvin Buckley wrote:
>> Based on the feedback I had from my proposal for function arguments =
in
>> errors last week, I'd like to introduce an RFC for it. Please let me
>> know what you think and please raise any possible issues.
>> https://wiki.php.net/rfc/display_error_function_args
>=20
> Thank you for the RFC. I have the following comments:
>=20
> 1.
>=20
> I believe there is almost never =E2=80=9CNo Impact=E2=80=9D to the =
ecosystem. In fact the RFC partly acknowledges it in the =E2=80=9CBackward=
 Incompatible Changes=E2=80=9D section. Even if the corresponding =
sub-vote to default to 1 doesn't pass, code needs to be prepared for =
someone to set it to 1 themselves. This includes off-the-shelf software =
(such as WordPress, or Drupal, or whatever).

I'm adding this to the ecosystem impact section.

> I have the following two suggestions (that follow pretty naturally, =
but are nevertheless an impact that should be spelled out):
>=20
> a) Custom error handlers (set_error_handlers()) need to be prepared =
for the error message format to change. Even though we don't make any =
guarantees about error messages themselves, the existing format with =
=E2=80=9Cfunction name first=E2=80=9D is reasonably structured for =
automated parsing (e.g. using a regular expression). This also includes =
error tracking tools that try to group error messages by function or =
similar.
>=20
> b) System administrators have one more INI setting to deal with and =
need to make a decision. Previous versions of the RFC template had an =
explicit =E2=80=9CINI setting=E2=80=9D section, but given it's so rare =
we add new INI settings these days, it has been removed from the =
template. For the few that still add one, properly discussing the =
consequences still is valuable.

I do recognize that PHP has been trending towards fewer knobs;
unfortunately, I don't see a better way other than adding a new
knob.=20

> 2.
>=20
> As for the naming of the bikeshed, I suggest `error_ignore_args` for =
consistency with `zend.exception_ignore_args`.

I'm not attached to the name; if others think this sounds good, I'll
adjust the RFC and PR.

> 3.
>=20
> For the voting options: You need to define a tie-breaker for the =
secondary votes.

I might be a little dense here; I see tie-breakers mentioned in
feature-proposals, but I don't see any guidance on how to include them
in an RFC. The other RFCs I've been skimming don't seem to mention them
either.

> Best regards
> Tim D=C3=BCsterhus