Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24355
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=JEXvE6BGm5dzrfW0n1DNppjV9EnyvM3m0VxEs6x+uu6aLxKxyfC6mdcqUepnViDM2NHl2ygWcOxYbodAcatX0aMR3zJXiSoGAzXRkK2FaP2AXLmUWJHLZAHCTM+sAEAE/hnBMtYO5aH8pQCf89MySwTZ3Q3pKaIe8j0E9zLwvfk=
Message-ID: <fe05d1540607121211m2592351ct3b929e246bb5b209@mail.gmail.com>
Date: Wed, 12 Jul 2006 21:11:57 +0200
To: "Lukas Smith" <lsmith@php.net>
Cc: internals@lists.php.net
In-Reply-To: <0F.C0.46743.0CB15B44@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <0F.C0.46743.0CB15B44@pb1.pair.com>
Subject: Re: [PHP-DEV] E_STRICT
From: pierre.php@gmail.com (Pierre)

Hello,

On 7/12/06, Lukas Smith <lsmith@php.net> wrote:

> Adding such a filter API into PHP internals however seems like a
> considerably effort. Therefore my proposal would be to simply add a
> defined "header" to all E_STRICT messages that contains the PHP version
> in which this E_STRICT message was added. This way PEAR could provide
> its developer with a simple filter method that would take an error
> message inside a customer error handler and determine if it should be
> filtered out or not.
>
> What do you guys think?

It sounds like killing a tank with a fly, or the other way 'round.

A E_STRICT fix does not break BC for a given package ([e]Z[end], pear,
or foobar framework). Why not simply release a bug fixes release of
this package?

I think it is reasonnable to ask users to update to support the latest
php releases (if they care about E_STRICT messages). As long as the
E_STRICT additions are loudly and clearly listed in NEWS, Changelog
and in the releases notes.

Attention, that does not mean I like to open the doors to even more
pedantic E_STRICT additions :-)

Cheers,
--Pierre