Something I've been meaning to get around to for a long time: a "contrib" module system for SBCL

Something I've been meaning to get around to for a long time: a "contrib" module system for SBCL. This is for "code which does not form part of SBCL itself, but which is sufficiently closely associated with it that it would not be sensible to run it as a completely separate project". Which is to say, code that gets its hands dirty with SBCL extensions or internals. So far we have a BSD socket library, a defsytsem, and (thanks to Kevin Rosenberg) an ACL-style toplevel, all of which can be called up using REQUIRE. More info from contrib/STANDARDS in the SBCL source tree.

Now I'm trying to figure out what the status of CLX is these days.

This blog has no comment-publishing facility: it's all done by hand. Feedback is welcome, though: if you would like to get in touch, email me on comment2010 @ telent . net and I will publish your thoughts (unless you tell me you don't want me to) as an addendum to the article, provided only that in my view they are interesting, amusing, relevant, accurate, or (best) some combination of the four. Relevant links are welcome in support of your argument: spam and untargeted requests for help are not.