Import handlers: Difference between revisions
Jump to navigation
Jump to search
Restored page from Google Cache, uploaded by John Pye |
No edit summary |
||
| Line 1: | Line 1: | ||
When you write an <tt>IMPORT</tt> statement in your model, the 'import handler' mechanism is invoked. | When you write an <tt>IMPORT</tt> statement in your model, the 'import handler' mechanism is invoked. | ||
This will search your <tt>ASCENDLIBRARY</tt> path looking for files with recognised extensions that can be loaded to provide additional [[External_libraries| | This will search your <tt>ASCENDLIBRARY</tt> path looking for files with recognised extensions that can be loaded to provide additional [[External_libraries|external library]] ASCEND functionality, such as blackbox external functions, external methods, [[External_Integrators|external Integrators]] and [[External_Solvers|external Solvers]]. | ||
The import handler mechanism allows various types of files to provide these things. The [[ExtPy]] mechanism has already been used to allow Python scripts to provide external method functionality. | |||
[[Category:Development]] | |||
Revision as of 01:34, 17 May 2010
When you write an IMPORT statement in your model, the 'import handler' mechanism is invoked.
This will search your ASCENDLIBRARY path looking for files with recognised extensions that can be loaded to provide additional external library ASCEND functionality, such as blackbox external functions, external methods, external Integrators and external Solvers.
The import handler mechanism allows various types of files to provide these things. The ExtPy mechanism has already been used to allow Python scripts to provide external method functionality.