Talk:JRuby Compiler

From JRubyWiki

looking forward to removing the disability caused by not being able to compile class definitions

Compiler complete now...

Probably needs an update now that the compiler handles all nodes (as of Thursday 27 Sep 2007) woohoo!

Impact of Reflection?

I attempted to use a previous version of (non-compiled) JRuby to implement tests in a Java project, but encounterd issues due to the wrapping of JRuby objects inside of proxy/reflection wrappers. Specifically, I recall I was creating a JUnit TestCase but found that JUnit's reflection-based execution would not work. (TestRunner classes in JUnit look for methods with particular names to figure out what to run as part of a test, and this reflection was failing, I recall.)

So. I know that JRuby java objects are not identical to pure/simple java objects, but am not clear on the differences or how/if the AOT compilation addresses these issues. Can anyone shed some light on how AOT impacts Java/JRuby interoperability?

The AOT work is a half-way step. The remaining step will be a plugin to the AOT compiler to produce normal Java method signatures from Ruby code. This will allow presenting a Ruby class as a normal Java class without losing Ruby semantics. This is planned for post 1.1. Headius