Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107211
MIME-Version: 1.0
References: <CAF+90c_Ds+UNZB4hAi1989SRafb=d1JkP2q4pdwkUUXfcHrLCw@mail.gmail.com>
In-Reply-To: <CAF+90c_Ds+UNZB4hAi1989SRafb=d1JkP2q4pdwkUUXfcHrLCw@mail.gmail.com>
Date: Wed, 18 Sep 2019 18:28:24 +0200
Message-ID: <CAF+90c90=zrRwcDSP_hGeYsw-Q=1M8JSYG1KWp-im1bOYuzJRQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007199270592d65444"
Subject: Re: [VOTE] Reclassifying engine warnings
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000007199270592d65444
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 12, 2019 at 2:17 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I've opened the vote on //wiki.php.net/rfc/engine_warnings.
>
> There are 4 votes, all of them independent. The first 3 are for specific
> cases that were controversial during the discussion, the last one is for
> the remainder of the proposal.
>
> Voting closes 2019-09-26.
>
> Regards,
> Nikita
>

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.)

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?

Nikita

--0000000000007199270592d65444--