Declare global in called table goes away following lookup?

[Fairlight]

On Sun, Aug 19, 2007 at 05:40:58PM -0400, Brian K. White may or may not have
proven themselves an utter git by pronouncing:
> I think we need a new term for one or the other meanings of global, like for 
> ,g I think it should really be called "persistent" even though it will have 
> to continue to be indicated with ",g".
> The long variable meaning for global is really what global usually means and 
> is more correctly named.
> 
> Even consulting thesaurus.com I can't find a word that means persistent but 
> starts with g.

I don't think you need to think of it in terms of starting a word with a
'g'.  I personally don't think of it that way at all.  Internally, I think
of it as a boolean flag that's either there or not, no different than a 1
or 0--it'll either perform with the functionality or without.

How I think of what it denotes is "temporal", since it's not so much
a matter of scope as it is in persistancy over -time-.  Since actions
that could wipe a non-g variable also occur over time and demarcation
threshholds within it, time is the common thread between everything in this
context, IMHO.  Hence "temporal".

mark->
-- 
The latest synth mixdown...
http://media.fairlite.com/Isolation_Voiceless_Cry_Mix.mp3