SAM has libraries. One library, SAM.tool comes
pre-installed. The user may install as many additional libraries
as desired. These may come from me or from anyone. You may
make your own.
It is important to understand, that libraries are a convenience,
and that is all. They are abstractions which provide a consistent
interface to menus.
SAM.tool, for example, is represented by the library
$lib/tool. The commands of the library can
be added to the PATH by:
bound $lib/tool
and by variations on the above. You may do this, and you
should just to see what happens, although it isn't necessary when it is
already referenced in the corresponding init file.
Let me explain a little. SAM can be started by
begin in the root of SAM or by a symlink in a
dual directory. In either case the default
bprofile,
init and
lib are the ones in the corresponding
directory (either the root of SAM or the
dual directory).
SAM refers to
bprofile,
init, and
lib using
$bprofile,
$init, and
$lib and thus
makes sense of this.
To configure SAM so that a library is automatically added to the
PATH when SAM is started, simply reference it in the corresponding
init file. The init in the
distribution comes pre-configured with a reference to
$lib/tool:
echo : $lib/tool final
To learn more about the libraries of SAM and about the SAM.tool
library, please read the GUIDE which is included in the
distribution.