Uwe Kubosch wrote:
On Sat, 2008-08-02 at 23:20 -0500, Charles Oliver Nutter wrote:
- You can only catch java.lang.Exception subtypes right now...should I
allow all Throwables?
Yes, why not?
Throwable includes all java.lang.Errors, which generally you don't ever
want to catch -- do
Uwe Kubosch wrote:
On Sat, 2008-08-02 at 23:20 -0500, Charles Oliver Nutter wrote:
- You can only catch java.lang.Exception subtypes right now...should I
allow all Throwables?
Yes, why not?
Mostly I was trying to avoid interfering with languages or frameworks
that use Error subtypes for int
On Sat, 2008-08-02 at 23:20 -0500, Charles Oliver Nutter wrote:
> - You can only catch java.lang.Exception subtypes right now...should I
> allow all Throwables?
Yes, why not?
Uwe
-
To unsubscribe from this list, please visit:
Charles Oliver Nutter wrote:
3. rescue can now rescue Java exceptions directly
...
It's working correctly for both interpreted and compiled logic.
Basically this just adds a Java catch (Exception e) to rescue logic so
any exceptions passing through will be inspected, like all Ruby
exceptions
I just added some enhancements that are a little experimental but likely
to stay in. Discuss please :)
1. Exceptions that bubble all the way out of the main thread, when run
from the command line, are now reformatted Ruby-style:
➔ jruby -rjava -e "raise java.lang.NullPointerException.new"
sun
