Nick Sieger wrote:
> On 10/31/07, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
>>> That would explain it. So should we fix this or is it a "feature"?
>> Java support is an all or nothing side-effect. I am not sure you can
>> fix it short of rewriting all features scripting Java in Ruby in Java.
>> I think we should label it a "feature". :)
>
> I have been finding myself writing more implementation code for JRuby
> in Ruby, and it's only natural to use Java integration when doing so.
> Most of the features (signal, for one) are not critical path and so I
> don't expect to be a performance bottleneck.
>
> Hopefully this will be a good trend -- it's too painful to write Java
> code these days :)
>
> /Nick
In the dim and distant past we did have someone complain that java was
preloaded in jirb (due to readline support, which was then rewritten in
ruby). I'm not sure it was much more than a desire for "require 'java'"
to return 'true', and that's less of an issue these days.
Personally I prefer writing our extensions in ruby, so I like this trend :-)
Damian
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
