Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107218
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <CAF+90c90=zrRwcDSP_hGeYsw-Q=1M8JSYG1KWp-im1bOYuzJRQ@mail.gmail.com>
Date: Wed, 18 Sep 2019 21:44:11 +0200
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <1BB4FA3E-23F6-45CB-9B8F-8DA3C497981D@gmail.com>
References: <CAF+90c_Ds+UNZB4hAi1989SRafb=d1JkP2q4pdwkUUXfcHrLCw@mail.gmail.com>
 <CAF+90c90=zrRwcDSP_hGeYsw-Q=1M8JSYG1KWp-im1bOYuzJRQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [VOTE] Reclassifying engine warnings
From: claude.pache@gmail.com (Claude Pache)



> Le 18 sept. 2019 =C3=A0 18:28, Nikita Popov <nikita.ppv@gmail.com> a =
=C3=A9crit :
>=20
> I just realized that I missed one notice here, because it is generated =
from
> a different location: "Constant %s already defined" (The define/const =
will
> be ignored and the previous value used.)
>=20
> It would be great to have that as an exception for optimization =
reasons,
> but as it's only a notice right now ... what do people think about
> promoting it to a warning?
>=20
> Nikita

Since attempting to define an already defined constant fails to perform =
the expected operation (i.e., defining the constant to *that* value), I =
think that a Warning is very reasonable.

=E2=80=94Claude=