Next: 2. The CM model
Up: CM The SML/NJ Compilation
Previous: Contents
  Contents
This manual describes a new implementation of CM, the ``Compilation
and Library Manager'' for Standard ML of New Jersey (SML/NJ). Like
its previous incarnation, CM is in charge of managing separate
compilation and facilitates access to stable libraries.
Most programming projects that use CM are composed of separate
libraries. Libraries are collections of ML compilation units. These
collections themselves can be internally sub-structured using CM's
notion of library components.
CM offers the following features to the programmer:
- separate compilation and type-safe linking [AM94]
- hierarchical modularity [BA99]
- automatic dependency analysis [Blu99]
- optimization of the compilation process via
cutoff-recompilation techniques [ATW94]
- management of program libraries, distinguishing between libraries
that are under development and libraries that are stable
- operating-system independent file naming (with optional escape
to native file names)
- adaptability to changing environments using the path anchor
facility
- an extensible set of auxiliary tools that lets CM
seemlessly interoperate with other program generators, source-control
systems, literate-programming facilities, or shell-scripts
- checked version numbers on libraries
- (still rudimentary) support for access control
- access to libraries from the interactive toplevel loop
- sharing of code that is common to several programs or code that
is common to both user programs and SML/NJ itself
- management of (the sharing of) link-time state
- conditional compilation (at compilation unit granularity)
- support for parallel and distributed compilation
- facilities for generating stand-alone ML programs
- a mechanism for deriving dependency information for use
by other compilation managers (e.g., Unix' make)
- an API to access all these facilities at SML/NJ's interactive
prompt or from user programs
CM puts emphasis on working with libraries. This contrasts with
previous compilation managers for SML/NJ where the focus was on
compilation management while libraries were added as an afterthought.
Next: 2. The CM model
Up: CM The SML/NJ Compilation
Previous: Contents
  Contents
Matthias Blume
2001-07-19