Hello, On 7/12/06, Lukas Smith <[EMAIL PROTECTED]> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
