From: matz@... (Yukihiro Matsumoto)
Date: 2001-07-16T09:10:35+09:00
Subject: [ruby-talk:17894] Re: Trapping Ruby exceptions from C

Hi,

In message "[ruby-talk:17893] Re: Trapping Ruby exceptions from C"
    on 01/07/16, Tobin Baker <senderista@hotmail.com> writes:

|That was my first thought, until I saw that the fourth argument to
|rb_rescue had to be a VALUE.  You're saying it's OK to coerce a VALUE
|* to a VALUE?  I know any pointer can fit into a VALUE, but isn't this
|somewhat confusing programming style?  (Not to mention even more
|spurious compiler warnings :-)

Yes, I admit.  I want these arguments to be something like (void*),
but C does not have opaque type that accepts both pointers and long
integer (which VALUE's representaion type is).  I consider that as C
programming restriction.

|Is this done habitually in the Ruby source?

Yes.

							matz.