On Sat, May 18, 2002 at 07:47:52AM +0900, Michael Campbell wrote:
> Are you asking then if the exception behavior of "<=>" is
> inconsistent, or its implementation in the C source?  
> 
> The ruby code seems completely consistent to me.  <shrug>

Perhaps consistency not the problem.  However, if I implement my own ==
method, then I can choose whether to catch all exceptions.  If I use the
one in Comparable, all exceptions will be caught, whether I like it or
not.

My question is whether catching all exceptions is a desirable feature,
since it can make bugs hard to find.

(The reason I originally mentioned consistency was that I was thinking
that if Ruby catches exceptions for me with Comparable#==, then it
should catch exceptions for me with Foo#== as well.  I have since then
taken a long nap and realized that catching exceptions for Foo#== would
be a special case for the interpreter and would not be desirable at
all).

Paul