Some Lisp-Stat Projects

This page lists some current projects and work in progress related to Lisp-Stat.

Win32 COM Automation Interface
Allows Lisp-Stat to be used as a COM Automation server and client. A brief description of the system and a discussion on implementation issues is availabls in PostScript or PDF format. The full implementation document is also available in PostScript format (useful for printing just the interface description).
Win32 Utilities
Some miscellaneous Win32 utilities, including basic registry access.
Callbacks for the C Wrappers
A simple form of defining callbacks for use with the wrapper system.
New Byte Code Compiler
A new byte code compiler, documented as a literate program.
A new autoload facility.
Registering cleanup actions at GC time and when workspaces are saved/restored.
Weak Boxes
An implementation of weak references.
Native Pointers
Modifications to support Lisp access to native pointers and protect Lisp objects into which these pointers point from GC.
Dynamic Loading Issues
What I know (or don't know) about dynamic loading on different systems and some implementations of the dlfcn interface.
Shared Libraries
A new shared library mechanism built on the dlfcn interface.
Regular Expressions
A shared library interface to POSIX regular expressions.
A shared library providing basic socket functions.
HTTP Clients
Some code for communicating with an HTTP server. Uses the regular expressions and sockets libraries.
C Wrappers
Some code for generating interfaces to C code using shared libraries. The regular expression library uses this mechanism.
CVS Clients
Some notes on using CVS clients on MacOS and WIn95 to talk to a CVS server on UNIX.

The snapshot directory may contain the source code and executables for MacPPC and Win32 of the current (reasonably) development version of xlispstat. Use at your own risk :-). When using the executable be sure not to use an existing workspace since internals have most likely changed.

A ChangeLog converted from the CVS log information with rcs2log is available. I will try to remember to update it regularly.

You can use cvsweb to look at the cvs tree (well, in principle you can, but is it broken at the moment). Anonymous cvs access to the source tree is also available.

Luke Tierney