Structural Informatics Group (SIG) logo
Home | Projects | Demos | Downloads | Publications | Local Info | About Us | New site
Go to the first, previous, next, last section, table of contents.

Slisp Organization

This node describes the basic organization of the slisp file hierarchy. This same organization will be found in the slisp archive and in all downloaded copies.

Slisp is organized as a file directory called slisp consisting mostly of a set of modules, each contained within a subdirectory. One of the modules is xcore, the basic xlisp interpreter written by Dave Betz. Each of the other modules (each starting with x, i.e. xetc) is a set of c and or lsp functions for implementing a new module.

An slisp application is defined by a subdirectory within slisp (say sl, for the basic sl application), whose name is the name of the application, and which contains configuration information, documentation, and generated files specific to the application. This organization allows more than one application to be built within the same directory hierarchy by simply creating a new application directory.

The files within each application directory are described in section Creating a New Application.

The files within each module are described in section Creating a New Module.

The following additional files and directories are present in all slisp distributions:

In addition to the directories within the slisp hierarchy, the configuration scripts Sconfigure and Smake will create files within $HOME/bin and $HOME/lib. The idea is that no derived files (such as o files or libraries) should be created in the source slisp directory, so that multiple machines can access a single nfs mounted source directory, yet create machine and application-specific binary files. The files created are:


Go to the first, previous, next, last section, table of contents.