At the last count there were n independently maintained CLX ports for
various Lisp platforms. This works pretty well given that most of
them are probably embedded into CL products, but on the other hand is
awkward if you're a user who finds a bug and wants to get it fixed in
all CLX variants, or you'd like to work on X extensions or similar and
wonder where to send the code.
prtable-clx-devel is a new mailing list for CLX bug reports and
patches, so that they can be reviewed and applied by the various port
maintainers. To be any use, this requires of course that the CLX port
maintaiers are subscribed. I'm publicising this to everyone I know of
who is or has been developing a version of CLX based on the MIT
sources, or is writing software that runs on CLX who might want to
report bug reports or fixes. If you know of other people or
organisations who fit this description, please feel free to alert them
as well. CLX hackers working for commercial Lisp vendors are welcome.
Find subscription information and past posts (some patches available
already) at
http://clozure.com/cgi-bin/mailman/listinfo/portable-clx-devel
Thanks to Gary Byers at Clozure for setting up the list and archives
-dan
--
http://www.cliki.net/ - Link farm for free CL-on-Unix resources
From: Kenny Tilton
Subject: Re: Announce: mailing list for CLX development co-ordination
Date:
Message-ID: <3E46BB00.7020105@nyc.rr.com>
Daniel Barlow wrote:
> At the last count there were n independently maintained CLX ports for
> various Lisp platforms. This ....
...seems like a Message From God(tm). LW is fighting me tooth and nail
refusing to do Cello (one FFI surprise, one multi-processing surprise,
and some surprise to be named at a later date when I find out what the
hell it is).
At the same time I am looking at GLUT (FreeGlut to be precise) and
thinking, jeez, I could port that (well, the Win32 variant) to CL in a
week.
New activity on CLX just about pushes me over the edge. I want to get
LW+FreeGlut working out of curiosity as to what is the problem, but it
really would be great not to have that wadge of C driving what is meant
to be a CL GUI. And callbacks from C do not seem to be a shoe-in for
every CL implementation, so there's another win.
One fun thing will be to have FreeGlut versions side by side in C and CL.
kenny
clinisys