Re: Exceptions in Soot

[Ondrej Lhotak <olhotak@sable.mcgill.ca>]

There was such a thing: CompilationDeathException. However, lots of
people didn't use it, possibly because it was so long to type. In most
cases where RuntimeException is used, it signals something that
shouldn't ever happen (basically an assertion failure), rather than
a user error.

What would you suggest that Soot do with a SootException (customized by
options), other than the current stack trace and abort?

Ondrej

On Tue, Aug 19, 2003 at 06:12:17PM -0500, Manoj Plakal wrote:
> 
> I've noticed that Soot throws
> a bare RuntimeException in many
> places to signal an error.
> 
> Have you considered throwing
> your own SootException and have
> it's behavior be customized with
> Soot options? E.g., perhaps
> you could be dropped into a
> Beanshell instance to inspect
> heap-resident data (I do this
> right now with my Soot phases).
> 
> Manoj
>