On Thu, Jun 26, 2003 at 12:44:52AM +0900, D T wrote:
>    Yet An other JRuby ??  :-)

This approach is *very* different from JRuby. I am accessing Java
through the JNI and later using the reflection API to map all the
methods to Ruby.

It offers quite a good integration (although by necessity not as tight)
but has the following advantages:
 * uses matz' interpreter: faster as it is in C and you get bug-for-bug
   compatibility with itself :-)
 * easy to develop: I've written it in 2 days and have quite some things
   running in only 5000 lines of code.

Cons:
 * method dispatch to Java is slower at the moment (esp. w/ the current
   implementation), but I believe it can be done at least as fast as in
   JRuby if not faster.
 * integration won't be as tight, but should be good enough. In the
   worst case, you can do anything through the low-level JNI API.

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

It's computer hardware, of course it's worth having <g>
	-- Espy on #Debian