From: Matt Armstrong <matt@...>
Date: 2001-07-16T14:24:33+09:00
Subject: [ruby-talk:17903] Re: Trapping Ruby exceptions from C

matz@ruby-lang.org (Yukihiro Matsumoto) writes:

> 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.

In Unix98 (or some similar standard) has intptr_t and uintptr_t just
for this purpose.  Perhaps ruby portability would be slightly improved
if it tried to use uintptr_t for VALUE if it exists.