Hi,

In message "Re: Segmentation Fault - Ruby Garbage Collection"
    on 02/08/01, William Djaja Tjokroaminata <billtj / y.glue.umd.edu> writes:

|What I mean is, for the Ruby language itself, I think you will make effort
|so that the Ruby API is backward compatible in the future releases.  What
|about the RUBY C API?  Are you going to make effort so that they are
|backward compatible too?

The future Ruby (Rite) will *not* have compatible C API, but I plan to
provide the compatibility layer if possible.

|Also, is there any defined set of "official RUBY C API"?  Is it only all
|the functions/macros/structs listed in ruby.h and intern.h?

No and yes.

|The reason is, for efficiency purposes, sometimes I may want to get to the
|underlying C function directly, instead of calling "rb_funcall".  Probably
|to be efficient, I have to define my own structures and
|functions; however, often this is difficult as Ruby requires all
|user-accessible objects to be of type VALUE.

I'm not sure why it is difficult.  Could you tell me how difficult?

							matz.