next up previous contents
Next: 10.1 Time stamps Up: CM The SML/NJ Compilation Previous: 9. The pervasive environment   Contents


10. Files

CM uses three kinds of files to store derived information during and between sessions:

  1. Skeleton files are used to store a highly abbreviated version of each ML source file's abstract syntax tree--just barely sufficient to drive CM's dependency analysis. Skeleton files are much smaller and (for a program) easier to read than actual ML source code. Therefore, the existence of valid skeleton files makes CM a lot faster because usually most parsing operations can be avoided that way.
  2. Binfiles are the SML/NJ equivalent of object files. They contain executable code and a symbol table for the associated ML source file.
  3. Library files (sometimes called: stablefiles) contain dependency graph, executable code, and symbol tables for an entire CM library including all of its components (groups). Other libraries used by a stable library are not included in full. Instead, references to those libraries are recorded using their (preferably anchored) pathnames.

Normally, all these files are stored in a subdirectory of directory CM. CM itself is a subdirectory of the directory where the original ML source file or--in the case of library files--the original CM description file is located.

Skeleton files are machine- and operating system-independent. Therefore, they are always placed into the same directory CM/SKEL. Parsing (for the purpose of dependency analysis) will be done only once even if the same file system is accessible from machines of different type.

Binfiles and library files contain executable code and other information that is potentially system- and architecture-dependent. Therefore, they are stored under CM/ arch - os where arch is a string indicating the type of the current CPU architecture and os a string denoting the current operating system type.

As explained in Section 2.8, library files are a bit of an exception in the sense that they do not require any source files or any other derived files of the same library to exist. As a consequence, the location of such a library file should be described as being relative to ``the location of the original CM description file if that description file still existed''. (Of course, nothing precludes the CM description file from actually existing, but in the presence of a corresponding library file CM will not take any notice of that.)

Note: As discussed in section 6.1.2, CM sometimes looks for library files in CM/ version / arch - os. However, library files are never created there by CM. If several versions of the same library are to be provided, an administrator must arrange the directory hierarchy accordingly ``by hand''.



Subsections
next up previous contents
Next: 10.1 Time stamps Up: CM The SML/NJ Compilation Previous: 9. The pervasive environment   Contents
Matthias Blume
2001-07-19