I observed in the documentation that ROOT/CINT supports exceptions when
the exception being thrown is an object type. Fine, I thought, that's
really the most useful form of exception anyway, and wrote some
Root-based code using them.
Running the code interactively, I made a mistake and caused an
exception to be thrown, which was not caught. When this happened, the
entire ROOT executable terminated.
This is, I think, not the desired behavior when Root/Cint is being
controlled from the command line -- exceptions should probably be
caught at the outer loop, any executing macros terminated and the user
returned to the command prompt with a message indicating that an
uncaught exception was thrown.
How hard would this be to implement?
George Heintzelman
gah@bnl.gov