Charles Oliver Nutter wrote:
I think Java exception should be virutally or actually represented as
subclasses of Exception or we should have JI define Exception#=== to
return true for Java exceptions as well as for Ruby exceptions. My
preference would be toward the latter.
- Charlie (mobile)
Both of those alternatives sound much better than what's currently
there. I would probably prefer the former, but I'm not strongly biased.
On Aug 16, 2008, at 9:58, Ola Bini <[EMAIL PROTECTED]> wrote:
Hey,
So, I'm thinking about the new change that makes Java Exceptions be
outside the regular hierarchy of exceptions. This is quite nice in
many circumstances, but it's also kinda bad for many of the
circumstances where you want to catch everything and handle it
correctly. As a typical example: when spec:ji fails on a Java
exception, the whole test run immediately dies, because there is no
Java code that can actually catch the exceptions from Java without
extra code.
Is this really what we want?
--
Ola Bini (http://ola-bini.blogspot.com) JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
--
Ola Bini (http://ola-bini.blogspot.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
