K, so lets think about it a bit...
EXIT in CALL returns but in INCLUDE quits... Change or keep? I think it would be confusing to change it.
Var scope in CALL local but in INCLUDE the same as parent... CALL is like a GOSUB on a file level. Again, to change it would be confusing.
So... the only real benefit in using INCLUDE over CALL is when tokenizing, it generates a monolithic file. Otherwise, a not tokenized running would make CALL redundant if it were the same as INCLUDE.
If a monolithic file is the only desired effect, I think we should take it a step further with my MakeEXE idea to package it into a single EXE.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
