If CM encounters a member class name
that it does not know about,
then it tries to load a plugin module named $/
-tool.cm. If it sees a file whose name ends in suffix
for which
no explicit member class has been specified in the CM description file
and for which automatic member classification fails, it will try to
load a plugin module named $/
-ext.cm. The so-loaded
module can then register the required tool, thereby enabling CM to
successfully deal with the previously unknown member.
This mechanism makes it possible for new tools to be added by simply
placing appropriately named plug-in libraries in some convenient place
and making the corresponding adjustments to the anchor environment.
In other words, description files $/
-tool.cm and
$/
-ext.cm that correspond to general-purpose tools should
be registered either by modifying the global or the local path
configuration file or by directly invoking functon
CM.Anchor.anchor (see section 4.1.4). Actual
description files for the tools' implementations can then be placed in
arbitrary locations.