Re: Bug #15154 Updated: set_error_handler(): some parse errors not caught

yeah but it doens't catch errors like this ither... $blah = new NonExistanceClass(); thats not a parse error... i think it has to do with it won't catch errors with error type of E_ERROR.... im trying to catch some errors that i make from my extension with the type of E_ERROR and they dont catch.... it' will catch if i call php_error with E_USER_ERROR... or E_WARNING... - Brad --- Markus Fischer <mfischer@guru.josefine.at> wrote: > On Tue, Jan 22, 2002 at 08:47:54PM -0000, J.Kolakowski@students.mimuw.edu.pl > wrote : > > ID: 15154 > > Comment by: J.Kolakowski@students.mimuw.edu.pl > > Reported By: J.Kolakowski@students.mimuw.edu.pl > > Status: Bogus > > Bug Type: Scripting Engine problem > > Operating System: PLD Linux 2.4.16 > > PHP Version: 4.0CVS-2002-01-21 > > New Comment: > > > > Sorry, my mistake. It prints "Warning: Use of undefined constant ..." > > indeed. And does it mean we just cannot handle any parse errors? > > Think yourself, you cannot catch a -> parser error <- because > the code is only executed after the -> whole file <- has been > > successfully < parsed. It is impossible. > > -- > Please always Cc to me when replying to me on the lists. > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/