Re: Re: [VOTE] Reclassifying engine warnings
| From: | guilhermeblanco@gmail.com | Date: | Wed, 18 Sep 2019 16:32:06 +0000 |
| Subject: | Re: Re: [VOTE] Reclassifying engine warnings | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-107212@lists.php.net to get a copy of this message | ||
Nikita,
I'd suggest to wait until the current vote ends and then open a new
RFC to vote this one, otherwise it'll be disrupting.
Cheers,
On Wed, Sep 18, 2019 at 12:29 PM Nikita Popov <nikita.ppv@gmail.com> wrote:
>
> 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
--
Guilherme Blanco
SVP Technology at Statflo Inc.
Mobile: +1 647 232 5599