Bill Dortch wrote:
You might take a look at
http://svn.codehaus.org/jruby/branches/bdortch/attrs/src/org/jruby/runtime/builtin
-- this was my initial take on refactoring IRubyObject (including
parameterizing the "base" object type for an eventual move away from
requiring all objects to implement IRubyObject). I decided it was a bit
much for 1.1, but maybe not. See also
http://svn.codehaus.org/jruby/branches/bdortch/attrs/src/org/jruby/runtime/component
<http://svn.codehaus.org/jruby/branches/bdortch/attrs/src/org/jruby/runtime/component>
for a plug-in implementation of ivars (I didn't get constants/cvars done
as I abandoned the work at that point).
Note that the code is a little stale and probably doesn't exactly map to
what got implemented in trunk. But it might serve as a useful
model/reference, or at least give us something to discuss.
Yes, looks remarkably similar :) And I think much of this can be done
for 1.1. The reason I'm looking into this now is fairly localized: I
want RubyException to be directly throwable as an unchecked exception.
But that means it has to extend RuntimeException or Error, not
RubyObject. By simplifying this interface, I should be able do that.
I'm taking a similar approach to what you were doing, so I may proceed
with it. And I think lightweights/dispatch on java.lang.Object is going
to be the last big frontier for making Ruby and Java integrate seamlessly.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
