Re: [Jruby-devel] Parameter name visibility for Java methods.

I guess we're going to disagree on whether parameter names should eternally remain contractual or not, or subject to revision despite everyone's hope that that many be avoided. I see libraries and apps that code against param names to to be on the periphery for Java, never the main stream.

Re: [Jruby-devel] Parameter name visibility for Java methods.

On 7/17/06, Paul Hammant <[EMAIL PROTECTED]> wrote: I guess we're going to disagree on whether parameter names shouldeternally remain contractual or not, or subject to revision despiteeveryone's  hope that that many be avoided. I see libraries and appsthat code against param names to to be on the p

Re: [Jruby-devel] [Jruby-user] JRuby compiler

On 7/17/06, Ola Bini <[EMAIL PROTECTED]> wrote: Let's see if I understand more or less how this would work. The blockclosures seem to be more or less like how lexical variables in Lisp areusually compiled.You've more or less got it. There's only a few differences in what I think we'll end up doing:

Re: [Jruby-devel] Parameter name visibility for Java methods.

Drifting further off topic, but oh well...On 7/17/06, Charles O Nutter <[EMAIL PROTECTED]> wrote: The other half of this is that named parameters *may* increase readability, but I don't think that's the real purpose. 99% of the method calls I make are passed mostly variable names. How could fetchRe

Re: [Jruby-devel] [Jruby-user] JRuby compiler

Charles O Nutter wrote: > > - Rather than allocating a frame per-call, as you do with new > IRubyObject[1], there would be a single per-thread stack (implemented as > an array/list) from which we'd allocate our frame. This eliminates one > more object allocation per-call. Where today we instant

Re: [Jruby-devel] [Jruby-user] JRuby compiler

On 7/17/06, Ola Bini <[EMAIL PROTECTED]> wrote: I can't really see where you would put that allocateFrame, if you don'tdo it on a per-call basis. Actually, maybe I'm using bad names in mycode, but I'm not talking about a heavyweight real object-Frame, but a frame which is a an array, so the most we

[Jruby-devel] JRuby 0.9.0 JRE 1.4 binary

I updated the sourceforge release of 0.9.0 to include a binary built using Java 1.4.2. It is called: jruby-bin-jre14-0.9.0.tar.gz Java 1.4 users rejoice! -Tom -- + http://www.tc.umn.edu/~enebo + mailto:[EMAIL PROTECTED] + | Thomas E Enebo, Protagonist | "Luck favors the

Re: [Jruby-devel] [Jruby-user] JRuby compiler

Charles O Nutter wrote: > > Closures are definitely made easier by having vars in multiple > IRubyObject[]...all they'd have to do is hold a reference to that frame. > If the method ends before the closure is called, it's no longer on the > Ruby frame stack...but it's still accessible in its f

Re: [Jruby-devel] [Jruby-user] JRuby compiler

On 7/17/06, Ola Bini <[EMAIL PROTECTED]> wrote: Just a quickie answer to your last point. I believe (without any greatdata for it right now) that to support real closures with the"single-array-model" we would have to jump through some _really_ strange hoops to get it working, or actually copy the r

Re: [Jruby-devel] [Jruby-user] JRuby compiler

Charles O Nutter wrote: > On 7/17/06, *Ola Bini* <[EMAIL PROTECTED] > wrote: > > I think the single-array-per-call would work just fine...but we have > some other considerations too like handling argument lists, passed > blocks and block args, and ensuring constant look

Re: [Jruby-devel] [Jruby-user] JRuby compiler

On 7/17/06, Ola Bini <[EMAIL PROTECTED]> wrote: Charles O Nutter wrote:> On 7/17/06, *Ola Bini* <[EMAIL PROTECTED] [EMAIL PROTECTED]>> wrote:>> I think the single-array-per-call would work just fine...but we have > some other considerations too like handling argument lists, passed> blocks and block

Re: [Jruby-devel] [Jruby-user] JRuby compiler

Charles O Nutter wrote: > On 7/17/06, *Ola Bini* <[EMAIL PROTECTED] > wrote: > > An interesting side note is that args are just local vars in Java...0 is > self for non-static methods, 1, 2, 3 would be the first, second, and > third args, and anything beyond that is a "

Re: [Jruby-devel] [Jruby-user] JRuby 0.9.0 JRE 1.4 binary

Hello, The sourceforge link go from http://prdownloads.sourceforge.net/jruby/jruby-bin-jre14-0.9.0.tar.gz?do wnload To http://prdownloads.sourceforge.net/redir.php And says the page cannot be displayed. I was able to download the the other file from http://prdownloads.sourceforge.net/jruby/jruby-

Re: [Jruby-devel] [Jruby-user] JRuby 0.9.0 JRE 1.4 binary

On Mon, 17 Jul 2006, Yemi I. D. Bedu defenestrated me: > Hello, > The sourceforge link go from > http://prdownloads.sourceforge.net/jruby/jruby-bin-jre14-0.9.0.tar.gz?do > wnload > To > http://prdownloads.sourceforge.net/redir.php > And says the page cannot be displayed. I was able to download th

Re: [Jruby-devel] [Jruby-user] JRuby 0.9.0 JRE 1.4 binary

Hello, Yes you are right. I had to use the USA Virginia link instead. Thank you. Good day. Yemi Bedu P&R Fasteners 325 Pierce St Somerset, NJ 08873 732-302-3600 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas E Enebo Sent: Monday, July 17, 2006

[Jruby-devel] Fwd: RDT doesn't like $~

Thomas and Charles, We got this bug report in. I haven't tried it against the latest JRuby codebase myself, so it might not still be a problem, but this should be valid Ruby code (I think). Thanks, Chris On Jul 10, 2006, at 2:54 AM, Bret Pettichord wrote: > Thanks for your work with RDT.

Re: [Jruby-devel] Fwd: RDT doesn't like $~

Captured as JRuby-25: http://jira.codehaus.org/browse/JRUBY-25 It is not fixed in trunk. Probably not too tough to fix either. -Tom On Mon, 17 Jul 2006, Christopher Williams defenestrated me: > Thomas and Charles, >We got this bug report in. I haven't tried it against the latest > J