As an alternative to CM.make or CM.autoload, where the main purpose is to subsequently be able to access the library from interactively entered code, one can instruct CM to load libraries ``for effect''.
val load_plugin : string -> bool
Function CM.load_plugin acts exactly like CM.make except that even in the case of success no new symbols will be bound in the interactive top-level environment. That means that link-time side-effects will be visible, but none of the exported definitions become available. This mechanism can be used for ``plug-in'' modules: a core library provides hooks where additional functionality can be registered later via side-effects; extensions to this core are implemented as additional libraries which, when loaded, register themselves with those hooks. By using CM.load_plugin instead of CM.make, one can avoid polluting the interactive top-level environment with spurious exports of the extension module.
CM itself uses plug-in modules in its member-class subsystem (see section 11). This makes it possible to add new classes and tools very easily without having to reconfigure or recompile CM, not to mention modify its source code.