> Unfortunately I am developing under another
> app/environment which assumes memory is somewhat cheap
> and plentiful ;). We use Allegro Common Lisp to host
> our language+development environment, and it isn't
> long before the lisp system has chewed up nearly all
> available memory, and certain operations will use up
> all available virtual address space even. We run at
> the theoretical limit of the Windows memory system (2
> Gb per user process). As for garbage collection... its
> a bit of a joke. We have to restart if it comes to
> Anyhow, I'm looking into adding a mode to J for our
> language (which is Lisp-like). And then I have to see
> how to connect J to Allegro CL under windows, which
> doesn't seem straightforward. Allegro comes with all
> kinds of Emacs lisp files to help connect it to emacs,
> so I know there's some work to do...
Well, in some sense j supports Lisp shells. I typically run Allegro
under j, and there are ways to send defuns and/or selected regions
directly from a j source buffer to the Lisp process (evalRegionLisp,
mapped by default to Ctrl Alt R, and evalDefunLisp, mapped by default
to Ctrl Alt E in Lisp mode buffers).
Unfortunately this is not documented well (or maybe at all, except for
the source in LispShell.java and LispShellMode.java), and in the
general case it requires jpty, which on Windows requires Cygwin...
If you want to take a look at this, you should get the lastest 0.18.0+
http://armedbear.org/j-jar.zip (just j.jar)
You'll need the source in j.zip if you want to build jpty (it's not
part of the binary distribution).
Alt X, "lisp" will run j's built-in toy Lisp, whose only real virtue is
that it doesn't require jpty... ;)
This stuff is currently under heavy development and for the most part
was not in the 0.18.0 release.