Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
Tricky.
Because INCLUDE is processed during the parse phase variables do not have values and are not evaluated. This is the reason that you cannot use variables in the INCLUDE path.
For a conditional include you should be using CALL - if you are concerned about the overhead overhead of repeated CALLs there are a couple of techniques that you can use to keep the code local.
You only need to use INCLUDE if you intend to create a monolithic tokenised script.
Do you have a specific example in mind where you cannot use CALL?
Code:
If Not IsDeclared($GLOBAL_DEFINE)
Call @SCRIPTDIR+"\Inc\Header\Globals.h"
EndIf
simple. you have multiple scriptlets that all have requirements and thus have include line in them.
now, when you create your huge application based on kixtart that uses those scriptlets, you currently need to remove all the include lines from all the files and add them to the main file. either main script or main library. anyhow, lots of work for that sorta approach.
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
Quote:
now, when you create your huge application based on kixtart that uses those scriptlets, you currently need to remove all the include lines from all the files and add them to the main file
No you don't - I've been using conditional CALLs as a replacement for #IFDEF / #INCLUDE in main and sub-scripts ever since we got IsDeclared().
It is only a problem if you are going to tokenise the main file and the included scriptlets, otherwise the combination of CALL and IsDeclared() will do the job just as well.
In fact CALL is the generally going to be the better option, as you can use variables and macros in the path which can only be determined at run time.
The only other reason that I can think that you need include is if you want to declare local variables that you are then going to use in the main script. Not a good idea IMO.
