Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128869
Content-Type: text/plain; charset=utf-8
Message-ID: <1760903162229.3857347732.451597939@yahoo.de>
To: tim@bastelstu.be
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Deprecate Undefined Constant Usage in php.ini Files
 (GH-20060)
Date: Sun, 19 Oct 2025 19:47:25 +0000
In-Reply-To: <b5048a1a-7787-4832-a14c-c67a56fa667c@bastelstu.be>
References: <b5048a1a-7787-4832-a14c-c67a56fa667c@bastelstu.be>
User-Agent: Vivaldi Mail/7.6.3797.63
Content-Transfer-Encoding: quoted-printable
Precedence: list
MIME-Version: 1.0
From: hanskrentel@yahoo.de (Hans Krentel)




On Sunday 19 October 2025 21:14:00 (+02:00), Tim D=C3=BCsterhus wrote:

> Hi
>=20
> On 10/5/25 14:54, Hans Krentel wrote:
> > The php.ini file parser (as used by `parse_ini_file()`) supports
> > constant resolution, including core predefined constants. However, the
> > current behavior with undefined constants is inconsistent with PHP 8's
> > strict handling of undefined constants in regular PHP code.
>=20
> How would PHP differentiate between =E2=80=9Cconstants=E2=80=9D and =
=E2=80=9Cunquoted strings=E2=80=9D, the latter of which are explicitly =
supported (and encouraged) by the INI file format?
>=20

As it does today, no change. If you use a word that would expand to a =
constant name as it does today, you need to quote it.

This preparatory step - if required - can be done in advance and the =
configuration file remains forwards / backwards compatible so can be used =
across versions (e.g. configuration file templates).

Best,

-- hakre