next up previous contents
Next: 11.3.2 Explicitly loaded, local Up: 11.3 Plug-in Tools Previous: 11.3 Plug-in Tools   Contents

11.3.1 Automatically loaded, global plug-in tools

If CM encounters a member class name $c$ that it does not know about, then it tries to load a plugin module named $/$c$ -tool.cm. If it sees a file whose name ends in suffix $s$ 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 $/$s$ -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 $/$c$ -tool.cm and $/$s$ -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.


next up previous contents
Next: 11.3.2 Explicitly loaded, local Up: 11.3 Plug-in Tools Previous: 11.3 Plug-in Tools   Contents
Matthias Blume
2001-07-19