[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread Patrick Wright
Because of this I'd like to use a Lisp dialect to add scripting. Right now, I'm looking mostly at SISC and Kawa. I don't know if the author(s) of SISC are following this list--I don't recall them speaking up or presenting SISC--an invitation to them might be in order. Patrick

[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread David Huebel
On Tue, Apr 29, 2008 at 5:08 PM, Randall R Schulz [EMAIL PROTECTED] wrote: Does the application use classloaders in interesting ways that might trip up the language implementation? My application does not, but the fact that its deployed in a servlet container might make the answer a de

[jvm-l] Re: avoiding boxing

2008-04-30 Thread Jochen Theodorou
Attila Szegedi schrieb: On 2008.04.30., at 11:49, Jochen Theodorou wrote: Rich Hickey schrieb: On Apr 29, 5:36 pm, Jochen Theodorou [EMAIL PROTECTED] wrote: [...] I think the answer is tags, as John Rose discussed here: http://blogs.sun.com/jrose/entry/fixnums_in_the_vm That, standard

[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread Rich Hickey
On Apr 30, 2:06 am, Per Bothner [EMAIL PROTECTED] wrote: Perhaps a friendly merger might be possible? I think peaceful coexistence is more likely. Clojure has certainly ceded the backwards-compatibility ground. There was a time (you may not remember) when I was considering either

[jvm-l] Re: avoiding boxing

2008-04-30 Thread John Wilson
On 4/30/08, Attila Szegedi [EMAIL PROTECTED] wrote: On 2008.04.30., at 11:49, Jochen Theodorou wrote: Rich Hickey schrieb: On Apr 29, 5:36 pm, Jochen Theodorou [EMAIL PROTECTED] wrote: [...] I think the answer is tags, as John Rose discussed here:

[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread Charles Oliver Nutter
Rich Hickey wrote: On Apr 30, 2:06 am, Per Bothner [EMAIL PROTECTED] wrote: Perhaps a friendly merger might be possible? I think peaceful coexistence is more likely. Clojure has certainly ceded the backwards-compatibility ground. There was a time (you may not remember) when I was

[jvm-l] Introducing ioke

2008-04-30 Thread Ola Bini
Hi, So, I promised that I would write up a description of ioke, so here goes. This is mostly tentative right now, since the implementation is not at all finished, and I'm finding myself yak shaving all the time. ioke is a language for the JVM. It takes influence mostly from Io, Smalltalk,

[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread Randall R Schulz
On Tuesday 29 April 2008 14:07, Randall R Schulz wrote: ... Thanks everyone for the feedback, especially for being made aware of Clojure. I'll be looking into these three languages (in alphabetic order, of course): - Clojure - Kawa - SISC Randall Schulz

[jvm-l] Re: avoiding boxing

2008-04-30 Thread John Rose
On Apr 30, 2008, at 6:37 AM, John Wilson wrote: On 4/30/08, Attila Szegedi [EMAIL PROTECTED] wrote: On 2008.04.30., at 11:49, Jochen Theodorou wrote: I don't see how this will help me in Groovy. We use the Java types, so there is no need to represent a 20 bit integer. It doesn't help

[jvm-l] Re: avoiding boxing

2008-04-30 Thread Attila Szegedi
On 2008.04.30., at 20:59, John Rose wrote: On Apr 30, 2008, at 6:37 AM, John Wilson wrote: I'm rather unsure about the value of making changes like this to the JVM. The timescale from now to when they become useable is rather long (2-3 years to get into a released JVM then another 2-3

[jvm-l] Re: avoiding boxing

2008-04-30 Thread Charles Oliver Nutter
Jochen Theodorou wrote: Charles Oliver Nutter schrieb: [...] I see... maybe the JRuby problem is just very different from the Groovy problem here Well, not really...you box all arguments in arrays too, and you're paying a cost for that. Whether that cost is measurable in the face of

[jvm-l] Re: Choosing a Scripting Language for a Java Application

2008-04-30 Thread Charles Oliver Nutter
Rodrigo B. de Oliveira wrote: On Wed, Apr 30, 2008 at 4:17 PM, Brian Frank [EMAIL PROTECTED] wrote: projects now I can't imagine being that statically bound. My impression is that C#/.NET has similar (if perhaps slightly lessened) restrictions. I don't think .NET is any less dynamic