On Fri, 14 Jul 2006, Greg Beaver wrote: > Sean Coates wrote: > > Ilia Alshanetsky wrote: > > > >>Why not just define your own custom error handler and have it filter out > >>the error messages that you don't want to see... To me this would seem > >>like a easier approach, i would be against adding a in-language filter > >>for this. > > > > > > Inability to easily determine which errors come from which version of > > PHP (in userspace, or otherwise) aside, E_STRICT can't always be handled > > at runtime. > > > > I can't think of a situation in 5.1.x where this is the case, but in > > 5.0.x, the use of 'var' (instead of public|private|protected) caused an > > E_STRICT at compile-time: before a userspace error handler could have > > been registered. > > > > ... admittedly, this is abnormal, but I think we should keep it in mind > > anyway. > > This is not entirely accurate. A userspace error handler can catch > E_STRICT during parsing of included files and eval(). This is how we > make install-pear-nozlib.phar work with our PHP 4/5 compatible PEAR files.
Only if it is not in the main PHP script though. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
