Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130501
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: <d9e0446c32d1b551024bd7d4b0b1d05c@bastelstu.be>
Date: Mon, 30 Mar 2026 16:00:09 -0300
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <7D440981-F647-4432-B1C7-AE6FC36609F6@cmpct.info>
References: <939CFA28-A6FF-433F-85A0-B83345CEF4A6@cmpct.info>
 <0598E8E2-F795-45E4-9177-0CA1B1808008@cmpct.info>
 <d9e0446c32d1b551024bd7d4b0b1d05c@bastelstu.be>
To: =?utf-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
From: calvin@cmpct.info (Calvin Buckley)

On Mar 30, 2026, at 12:24=E2=80=AFPM, Tim D=C3=BCsterhus =
<tim@bastelstu.be> wrote:
>=20
> Hi
>=20
> Am 2026-03-30 16:40, schrieb Calvin Buckley:
>> If I don't hear any additional feedback, I think I'll open this for
>> voting at the end of the week.
>=20
> I've looked once more into my =E2=80=9Cnaming remark=E2=80=9D and =
realized that the `display_` prefix might actually be misleading =
(instead of =E2=80=9Cjust=E2=80=9D inconsistent) when compared to =
`display_errors` or `display_startup_errors`, because =
`display_error_function_args` does not control whether the arguments are =
*displayed*. It also controls whether or not the arguments are visible =
to a registered error_handler, which is quite different from just =
suppressing them from public display as done by `display_errors`.
>=20
> My suggestion of `error_ignore_args` thus still stands and I would =
likely vote against the RFC with the current naming (despite being in =
favor of the feature itself).
>=20
> Best regards
> Tim D=C3=BCsterhus

I've renamed the INI option per your suggestion. This does invert the
semantics (matching the one for exceptions), so I took some care when
editing. I'll update the PR accordingly soon.=