The cm class understands two kinds of parameters. The first is a named parameter labeled by the string version. It must have the format of a version number. CM will interpret this as a version request, thereby insuring that the imported library is not too old or too new. (See section 5 for more on this topic.)
Example:
euler.cm (version:2.71828) pi.cm (version:3.14159)
Normally, CM looks for stable library files in directory CM/ arch - os (see section 10). However, if an explicit version has been requested, it will first try directory CM/ version / arch - os before looking at the default location. This way it is possible to keep several versions of the same library in the file system.
However, CM normally does not permit the simultaneous use of multiple versions of the same library in one session. The disambiguating rule is that the version that gets loaded first ``wins''; subsequent attempts to load different versions result in warnings or errors. (See the discussion of CM.unshare in section 4.1.6 for how to to circumvent this restriction.)
The second kind of parameter understood by cm is a named
parameter labeled by the string bind (see
Section 3.3). It can occur arbitrarily many times
and each occurence must be a suboption-list of the form
(anchor:
value:
). The set of bind-parameters augments
the current anchor environment to form the environment that is used
while processing the contents of the named CM description file.