: |To get ruby 1.4.4 to compile with ccc, in eval.c line 726 in rb_eval's
: |prototype, the NODE* must be changed to NODE* volatile; the same for
: |line 732 in module_setup.  I believe this is also the case with 1.5.

...

: Extensions compiled by gcc seems to work fine.  Ruby compiled by ccc
: can load extensions compiled by gcc.  Probably ccc requires some
: option to be set to generate dynamic loadable object like -fPIC for
: gcc.  Information is welcome.

I found very little documentation on this.  ccc is supposed to convert
some gcc options to ccc ones; others it ignores.  I wasn't able to find
anything like -fPIC for ccc in the ccc docs, and compiling the modules
with and without -fPIC didn't make a difference as far as I could tell;
both worked.  So I don't know if the option was getting ignored or not. 

As long as the modules were compiled without -g (I tried -O2, but not
other optimization levels), gcc and ccc-compiled ruby were able to load
either's (and their own) modules fine.

Wes.

: Making newlines in parentheses work like Python introduces minor
: backward incompatibility.  Although I guess nobody use this syntax.
: 
: I think we should disscuss more before changing syntax.
: 
: 							matz.