- Our import would behave differently than Java's, so it seems better to use include_package and include_class to differentiate them
- 'import' could easily conflict with a future Ruby keyword or method if an alternative to the current require or include semantics is needed
I'm less opposed to it now, but I still don't think there's a good answer for either of these issues.
On 5/11/06, David Corbin <[EMAIL PROTECTED]> wrote:
On Wednesday 10 May 2006 08:26 pm, Charles O Nutter wrote:
> - In most cases, there will be a local filesystem involved
1) I have definate plans to try an applet
2) classes in jar files are not in the local filesystem.
> - We only look in one classloader even now, which should delegate to
> classloaders higher in the hierarchy anyway. Plus, we only need names
> of classes.
> - We can fall back on the "slow" way if anything fails.
'slow' way?
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
