Closed GoogleCodeExporter closed 9 years ago
Is that a runtime exception or something? I had made the assumption that there
will
always be a throws declaration.
Maybe I'll make a separate end point for runtime exceptions. Actually, I can
connect
the asserts up to that too, except they won't be labeled as an exception edge.
Would
that work?
Original comment by ciera.christopher
on 10 Jul 2008 at 2:40
New test cases are in.
Original comment by ciera.christopher
on 10 Jul 2008 at 5:55
New test cases are in.
Original comment by ciera.christopher
on 10 Jul 2008 at 5:55
Original comment by ciera.christopher
on 10 Jul 2008 at 5:56
Looks like this works for the code now that caused the problem for me. Yes, the
thrown exception was a runtime exception. Does this "runtime exception" exit
exist
now? I like the idea of hooking up asserts to this exit as well. As discussed
before, we could even label those edges with Throwable or Error.
Original comment by kevin.bi...@gmail.com
on 13 Jul 2008 at 7:05
Yeah, I committed the change. I hooked up asserts to this with the Throwable
label.
There's a public getter to this exceptional exit, separate from the declared
exceptions and the uber-return.
Original comment by ciera.christopher
on 14 Jul 2008 at 12:27
Original issue reported on code.google.com by
ciera.christopher
on 10 Jul 2008 at 2:32