And "top level" variables count as globals in this respect. If the
'global' declaration above is omitted, runNr still increments over
runs.
this is a surprise!
I think there was a bug in the earlier versions of Tiger, whereby
globals
and properties _didn't_ persist. But that's been fixed for a while
now.
To "remove garbage from a script between runs", you can set its
globals
to less bulky values (eg. "") before it finishes, or, preferably, use
locals instead.
Den 4. jun. 2007 kl. 15.42 skrev Luther Fuller:
I solve this problem by simply avoiding the use of globals. Always.
My run handlers always start with ...
I have a few files with my most used handlers. I have been used to
load them like this.
I know I will not change the value, just keep it within reach
everywhere, so I thought global was the way to go.
Is there a better way?
Håvard
--
global MyScriptLib
on run
my startup()
my dostuff()
end
on startup()
set MyScriptLib to load script alias somefile
end
--
