Hi Jeff,
Sorry for the late reply.
On Aug 13, 2010, at 11:59 AM, Jeff Hemmelgarn wrote:
> Alright!
>
> Thanks for all the help. I was able to track down the problem and have some
> changes for marshal.c that I need to get back to the repository. There were
> some assumptions about the sizes
Alright!
Thanks for all the help. I was able to track down the problem and have some
changes for marshal.c that I need to get back to the repository. There were
some assumptions about the sizes of types that were broken by going to 64-bit .
I don't know the procedures on this project. Do I n
Also, when debugging MacRuby it is better to use the version of libmacruby in
the build directory, because the installer strips symbols during installation.
From the build directory:
DYLD_LIBRARY_PATH=. gdb --args ./macruby ...
Also, the whole project is compiled with heavy optimizations which
Hi,
Good to know you're motivated to get into hacking MacRuby :D
`rb_marshal_load` is an "API", supposed to be used by extensions for example.
If you look in `marshal.c`, you'll see that the "load" method is defined by
`marshal_load` (without the rb_ prefix):
rb_objc_define_method(*(
Hello,
First I want to thank everyone involved in the project for their efforts in
bringing MacRuby to us. I love being able to use GCD with ruby! I have been
on vacation for a week and finally feel like touching a computer again so I
thought I would look into doing some MacRuby development.
