From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-06-26T01:22:07+09:00
Subject: Re: Ruby/Java integration through JNI: working implementation

On Thu, Jun 26, 2003 at 01:08:48AM +0900, james_b wrote:
> D T wrote:
> >Yet An other JRuby ??  :-)
> 
> Not quite, and the JNI route may have an advantage.
> 
> JRuby implments the Ruby 1.6.7 interpreter; we're on the verge of a 
> proper Ruby 1.8 release.  Perhaps it's less hard than I imagine,
> but updating JRuby with each change to the latest stable Ruby release
> is a task.
> 
> On the other hand, allowing calls into Java via JNI sidesteps this 
> problem.  I think, though, that it also sidesteps the ability to load 
> and execute Ruby scripts from Java. :(

You can always use JNI the other way around, to expose for instance
rb_eval_string_protect to Java. Then you have to wrap Ruby objects to
be able to manipulate them.

However in my mind it makes more sense to have Ruby driving everything
and using Java classes as needed.

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

Sic transit discus mundi
	-- From the System Administrator's Guide, by Lars Wirzenius