Re: parse errors when testing for undefined exceptions

in your function, you should assume sqlite is present. before calling any functions, have one of the first actions in your script (preferably in some file you include always anyway) be a check on the existance of sqlite. problem solved? "Alan Knowles" <alan@akbkhome.com> schreef in bericht news:4135C8C3.5000705@akbkhome.com... > 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