Handling of modules
The functionalities of Mosel may be extended by using native libraries or modules implemented as dynamic shared objects (DSO). The module manager of Mosel keeps a list of all loaded modules and maintains a list of references for each of them. Using the following functions it is possible to know which modules are currently loaded and what are the provided features, and to access the values of their control parameters.
|
Disable/enable automatic unloading of modules.
|
|
|
Find a DSO descriptor from a module name.
|
|
|
Unload unused dynamic shared objects.
|
|
|
Retrieve annotations defined by a module.
|
|
|
Get the current value of a control parameter.
|
|
|
Get the directory list where DSO files are searched for.
|
|
|
Get a property of a dynamic shared object.
|
|
|
Get next dynamic shared object.
|
|
|
Enumerate constants of a module.
|
|
|
Enumerate dependencies of a module.
|
|
|
Enumerate control parameters of a module.
|
|
|
Enumerate procedures and functions of a module.
|
|
|
Enumerate native types of a module.
|
|
|
Get the next IO driver in the list of available drivers.
|
|
|
Explicitly load the named module.
|
|
|
Declare a module as static.
|
|
|
Set the directory list where DSO files are stored.
|
© 2001-2024 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.