Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106755
MIME-Version: 1.0
References: <CAF+90c9Kc6m_bv=aJxbD3-RmnNXXLqv6mPjHp7U7qxX_ck27qw@mail.gmail.com>
 <CAKuGYLQC2z+GmOgbqxFWbAGS6B2z=mXTp72c6Be53ju4D6pNRw@mail.gmail.com> <CAJHtznxgkUFZ2os5Hx5rYmFCrATJ+LTOovK6W4J1cDw6oo45=w@mail.gmail.com>
In-Reply-To: <CAJHtznxgkUFZ2os5Hx5rYmFCrATJ+LTOovK6W4J1cDw6oo45=w@mail.gmail.com>
Date: Wed, 28 Aug 2019 13:20:27 -0400
Message-ID: <CAKuGYLQfg8CQOORWTO57Cfk92oM3DNmw0h9wt3jP9gSUCx+QWg@mail.gmail.com>
To: Zeev Suraski <zeev@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009f14680591309b6b"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: matthewmatthew@gmail.com (Matthew Brown)

--0000000000009f14680591309b6b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We log 1 in every 1000 notices, and yes - being notice-free is a goal =E2=
=80=93
though not one with any particular timeline at the moment, because we can
just ignore the problem. I look forward to not being able to ignore the
problem.

On Wed, 28 Aug 2019 at 12:55, Zeev Suraski <zeev@php.net> wrote:

>
>
> On Wed, Aug 28, 2019 at 5:22 PM Matthew Brown <matthewmatthew@gmail.com>
> wrote:
>
>> Looking at our notice logs, I estimate (fairly roughly) that it would
>> require about a week's worth of my time to fix these issues in vimeo.com
>> =E2=80=99s
>> 700K LOC codebase (the undefined variables are confined to our views).
>>
>
> Can you elaborate a bit about how you generally deal with notices in
> vimeo.com - are you generally aiming to be notice-free?  Or is that log
> collecting a huge amount of messages?
>
> Zeev
>

--0000000000009f14680591309b6b--