Re: [j-devel] Interest in J vs ABCL?

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

Forgot to send the mail below to the ML.

On Tue, Aug 12, 2008 at 4:30 PM, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
> On Tue, Aug 12, 2008 at 3:47 PM, Mark Evenson <ev...@pa...> wrote:
>> XXXXXXXXXXXXXX wrote:
>>>
>>> It's great to see the reactions of the past days. It's becoming clear
>>> I'm definitely not the only one with interest in ABCL.
>>>
>>> However, I didn't see anybody express the any concerns with the fact
>>> that my primary interest is with ABCL. Is there truely that little
>>> interest for J?
>>
>> Every time I have interest in J (i.e. I want to script Java Swing elements
>> from ABCL),
>
> That's something I'd like to do too, however, I don't really see what
> J can add to it, because ...
>
>> I end up rolling my own.
>>  But it is real nice to have J around to compare my implementation.
>
> I don't really understand this remark: I've looked at J just now
> (again) and it's 100% java (not 99.9, really 100%). What are you
> referring to? Is what you're referring to in J or in ArmedBear?
>
>>  I prefer to use the a little syntactic sugar
>> like
>>
>>  (#"registerCallback" object (lambda (arg) (display arg)))
>>
>> (this syntax was introduced by Alan Ruttenberg with [JSS][1].
>
> That's nice syntax, especially given the dynamic dispatch. I was
> working at doing something like it, but less advanced. It looks a bit
> like the CCL (aka OpenMCL) Lisp-Cocoa bridge.
>
> BTW: binding to Swing elements is not something I'd like to call "J".
> It's something that in the broader context of ABCL can be very useful.
> What I consider "J" is roughly the src/armedbear/j directory in the
> source tree: the editor (which looks inspired by emacs) with its
> supporting files. Do we have different definitions of "J"?
>
>> I don't think
>> this is any fault of J, but introducing a notion of "core" and "extension"
>> to ABCL would be very interesting for me, primarily in response to my
>> thinking of whether a Java Web Startable ABCL makes sense [abcld][2], and
>> then how to meaningfully limit the initial download.
>
> This seems like a nice project. Do you have any special uses in mind?
>
>
>
> Bye,
>
> Erik.
>