🚀 go-pugleaf

Well, a number of people, including David Betz, seem agreeable
to my attempting to coordinate a merge of the various extended
xlisp 2.1s, and I've gotten no (!) stay-off-my-turf flames.

At the moment, I have:

Stock xlisp2.1 from gatekeeper.dec.com.

Niels Mayer's xlisp2.1 from winterp-1.01.

Tom Almy's extended 2.1, via Niels & expo.

Ken Whedbee's extended version of Tom Almy's extended version...

Luke Tierney's xlispstat (umnstat.stat.umn.edu
   128.101.51.1  in ~pub/xlispstat)

Anything else I should look at?

Anyone have or know of a relevant validation or regression suite?

At the moment, what I think I'd like to produce would be a core xlisp
which:

1) Is stable, with all known bugfixes applied.

2) Can be compiled to produce a MINIMAL xlisp.

3) Can be compiled to produce a MAXIMAL xlisp. (I'm inclined to allow
only functions present in xlisp2.1 or Common Lisp, however.)

4) Can be extended to include other function libraries without
modifying the core xlisp fileset.

5) Can be embedded in a larger C application without modifying the
core xlisp fileset.

Suggestions? Comments? Flames?

Fair warning: Other than a pretty-printer/structure editor I wrote
back around 1978 (for a lisp I'd written in PDP-10 assembly in the
pre-hard-disk era :-), I've never actually written anything in Lisp.
Could be a learning experience...
--
jsp@glia.biostr.washington.edu (Jeff Prothero)
jsp@u.washington.edu (If above bounces.)
Biological Structure Graphics Lab, U Washington