Thanks for your answers.
I read the thread and understood why I don't get my
IllegalArgumentException but a new RuntimeException that wrapps it.
But I don't understand what the reason is to create a new
RuntimeException (stack tracing?) knowing that IllegalException is a
subclass of RuntimeExcep
On Thu, Jun 11, 2009 at 7:12 PM, peg wrote:
>
> Hi clojurians,
>
> I was happily clojure-coding whent I tried to catch a exception in a
> thrown deeply in a function.
>
> After looking for the fact that the IllegalArgumentException wasn't
> catch, I added a catch RuntimeException to my catch list
The Clojure run time throws IllegalArgumentException in a lot of
different places. It does also throw RuntimeException
in several places. It traps exceptions generically (catch (Exception e),
catch (Throwable t) ) and may have thrown a RuntimeException back
to upper layers instead of the original\
Hi clojurians,
I was happily clojure-coding whent I tried to catch a exception in a
thrown deeply in a function.
After looking for the fact that the IllegalArgumentException wasn't
catch, I added a catch RuntimeException to my catch list ... and that
worked of course.
Here is the simplified cas
