Re: parse errors when testing for undefined exceptions

From:	Alan Knowles	Date:	Wed, 01 Sep 2004 13:22:24 +0000
Subject:	Re: parse errors when testing for undefined exceptions
References:	1	Groups:	php.internals
Request:	Send a blank email to internals+get-12524@lists.php.net to get a copy of this message

aghh.. - another crap example: The priciple it was try to make was that .... require_once 'MyException.php' throw MyException(....); .... then trying to catch MyException leads to a parse error when it's try()'d and not loaded. Regards Alan Alan Knowles wrote:

This is a simple example of why making a parse error out of undefined Exception types is going to be very problematic. function test($a) { if (!extension_exists('sqlite')) {
       return;
} try {
       SQLite::query($a);
          // parse error!!! - if we dont have sqlite, we dont have SQLite exception!
} catch(SQLite_Exception $e) {
       echo "problem with query";
       return;
} } This has a big knock on effect that we can not lazy load Exception definitions, even if they are only used in Exceptional situations. (its pretty much the same issue as instanceof - forcing the loading of code, that may never be used, except to test it's non-existance.) Regards Alan