[Gdal-dev] CPLErrorV change to better support scriptland

Kevin Ruland kruland at ku.edu
Mon Jun 20 10:10:35 EDT 2005

>Certainly the error handlers installed can choose to do something
>other than returning if the error class is CE_Fatal.  But keep in mind
>that the error class is set to fatal because continued execution on 
>the main code path is not possible.  GDAL datastructures are likely
>to be arbitrarily invalid after such an error.  


That would certainly be true and it would be up to the programmer to
make sure they didn't do anything stupid, like ignore the exception.  In
the event of such an error, the script might have some important work to
do such as return an error page (in cgi applications) or close databases
or start a pot of coffee for a late night debugging session and the
premature abort() would prevent any action.

Actually, if the error was from malloc, there could be quite a bit of
invalidation throughout the interpreter.  Maybe this wouldn't be such a
good idea.


More information about the Gdal-dev mailing list