Re: [RFC DISCUSSION] Error Storage Behavior

From: Date: Mon, 27 Jun 2016 19:53:11 +0000
Subject: Re: [RFC DISCUSSION] Error Storage Behavior
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-94289@lists.php.net to get a copy of this message
Hi! > Currently error_get_last() always contains the last error that occurred, > however, this is actually not desired if the last error was an exception > that was caught. > > https://github.com/php/php-src/pull/1936 I think conditioning warnings on whether exception is caught or not is a very bad idea. However, having _either_ exception _or_ PHP error and not producing both (except in the case where uncaught exception becomes fatal error I guess) may be a good idea, but it needs careful checking of the implications. In general, old error mechanism and exceptions are not very good combination, and using them together may be troublesome. It's definitely not "just a bug fix" - it needs careful check of what exactly happens when. -- Stas Malyshev smalyshev@gmail.com

« previous php.internals (#94289) next »