On Oct 27, 2007, at 11:00 AM, Charles Oliver Nutter wrote:
This would fit with the typical .rb/extension pair in Ruby, where
a .rb file exposes some public utility APIs based upon the
interface implemented by an extension. The only difference here is
that the extension itself (java support) is a mix of Ruby and Java
code too. So we'll take all the code that would represent the
"extension" portion of JavaSupport--the bits that we'd eventually
want to be pure Java and that implement the "heavy lifting" of Java
integration--and keep those inside the JAR. The "utility" portions,
like the incorporation of java/javax/etc methods into Kernel and
the (possibly deprecated) "import" enhancement to include_class,
would go in the public API.
Reasonable?
Sounds great to me.
Also...on the "import" deprecation issue: we kinda made our bed in
1.0 by including "import", and we can't really deprecate it on the
1.0 line. But we could deprecate it in 1.1 and provide an
alternative. I'd feel better about that than saying it's deprecated
across the board.
It would be fantastic if the documentation on top of the import
method said something to that effect, and perhaps adds a reference to
what potential problems might be.
-- Tor
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
