Ah... OK, so if the File doesn't exist, an INCLUDE-Directive throws an error?
Correct, I've raised this before in the context of (interface units to) libraries etc. and was told that not only did such a thing not exist but that it wasn't going to happen.
The choices are either to write your own preprocessor ** or to use runtime library loading (i.e. put the optional code into a DLL/so).
** Which is not as far out as it sounds: preprocessor reads a list of files to check and emits its own .inc file with a $define for each file which was actually present. That file is included into each file of the project, at which point the $include directives can be guarded by an $ifdef.
MarkMLl