next up previous 63
Next: Implementation for Unix
Up: Interface Module Search Path, ADAM_IFL
Previous: Interface Module Search Path, ADAM_IFL


Introduction

By default, ADAM application programs attempt to find their Interface Module in the directory containing the executable file. A compiled (.ifc) file will be used in preference to a source (.ifl) file. To allow users to have different versions of the Interface Module for a given program without having multiple copies of the executable file, a search path mechanism has been implemented. This will be particularly useful for private tailoring of the Interface Modules of released software.

The search path is entirely the responsibility of the user - no value is defined in the standard system setup as there is a slight overhead in having one defined when it is not required.

If the search path is not defined, or an Interface Module is not found using it, the program will attempt to use the default.



next up previous 63
Next: Implementation for Unix
Up: Interface Module Search Path, ADAM_IFL
Previous: Interface Module Search Path, ADAM_IFL

ADAM Interface Module Reference Manual
Starlink User Note 115
A J Chipperfield, B D Kelly, S L Wright
3 September 2002
E-mail:ussc@star.rl.ac.uk

Copyright © 2002 Council for the Central Laboratory of the Research Councils