> > > We don't really have a choice, the C API does not offer all the features we > need and we also need to follow the new LLVM changes internally. Hopefully, > the LLVM team is always helping us :-) >
I wouldn't expect you to use the C API internally, but it's convenient to wrap it with FFI. That's how bindings were created for e.g. Lua and Ocaml. > Linkage may also be problematic since my FFI bindings depend on LLVM > dylibs. I'm not sure how they would work with MacRuby yet. > > > It will very likely collide at runtime... until we un-export all symbols > (but the C extension ones) from the link phase, which should happen in > theory for our next release, 0.6. > That sounds promising. Thanks for the explanation. Best, Jeremy > Laurent > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > >
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
