scope of variables in included scripts is easy. it is the same as if you would have written the included script inside your including script.

what comes to the var scope of tokenized script, I shall take a simple example. (to proof it to myself too on the fly):
Code:

;the mainscript that calls
global $c
$c = "EXPLICIT TEXT ON GLOBAL SCOPE"

call "GetsCalled.kx"

get $

Code:

;the script that gets called "getsCalled.kix"
$c ?


no, tokenize them both separately and run the mainscript.
you see it works just like it would without tokenization.

now, if you have some variable dependency - intended or not - in some tokenized subscript, it may lead to unexpected behaviour in some situations, like complex string manipulation when the input is not what it should be.

anyway, if it is not too much asked, I think someone would like to see a failing called tokenized scripts code to hunt the cause down.
I could volunteer for that.

cheers,
younger fart
_________________________
!

download KiXnet