On 3/3/2016 6:48 PM, Rowan Collins wrote:
> There's a subtle distinction which I may not have explained very well.
> What I want is the ability to *selectively* ignore these warnings. For
> instance, if I write:
>
> namespace \Foo\Bar\Baz;
> class AwesomenessFactory implements ArrayAccess {
> var $something;
> }
>
> ... then I would be happy to see a notice that I'd used the wrong keyword.
>
> But if I write:
>
> # TODO Replace dependency with modern equivalent
> include 'Ancient/PEAR/Library.php';
>
> ... then I don't want to see 500 notices that the library I'm about to
> replace has old-fashioned code in it. The same is true if I am actually
> maintaining the included library, and have a rewrite in the works which
> I am confident will supersede the current stable version long before the
> next major version of PHP.
>
> It's not about whether those notices are there for 6 years or 9 years,
> or which E_* constant they appear under, it's about granularity of which
> ones shout at me.The closest we have to achieve this is ignore_repeated_errors plus ignore_repeated_source. However, you would still get one entry per request/process/... https://secure.php.net/errorfunc.configuration -- Richard "Fleshgrinder" Fussenegger
signature.asc
Description: OpenPGP digital signature
