From: Adam Gardner Date: 2009-02-06T03:09:39+09:00 Subject: Re: Native gem roundup! Logan Barnett wrote: > On Feb 4, 2009, at 7:02 PM, Julian Leviston wrote: > >> The cocoa objective-c java bridge is deprecated from my >> understanding, and cocoa is copyright, so there'd be little point, >> tho I dunno why jruby couldn't theoretically run the cooaruby code > > I'm not sure about the deprecation, although that typically doesn't > mean much in the Java world (: > I don't understand what you mean by copyright (unless you mean that > you can't port it to another platform). > If the CocoaRuby stuff calls out to native C bindings, JRuby won't be > able to use it unless the bindings were made against FFI (I'm not sure > what the exact process is, but FFI extensions work great in JRuby, > whereas gems and other libs that depend on native C code don't work at > all in JRuby). I strongly believe that CocoaRuby uses native > extensions, but I could be wrong (: I'm not 100% sure of the low-level mechanisms involved, but I do know that RubyCocoa makes heavy use of FFI (that's libffi the C library, not ruby-ffi), along with a Framework/Library metadata system called BridgeSupport and a automatic generator of said metadata called gen_bridge_metadata.rb . That being said, I believe there are also some native extensions used in areas where metadata-based support was particularly thorny. -- Posted via http://www.ruby-forum.com/.