global problems

[Charles Hartman]

I agree (with everybody), of course.

But it is true that until this thread came up I didn't think to look  
in the Variable Watcher for signs of this. There were a couple of  
globals that I had declared at an earlier experimental stage of  
development of this project, still hanging around without making a  
peep. That does seem a little untidy.

But I guess this is a logical result of the (otherwise blessed)  
absence of a code-and-compile cycle. In a Transcript-like  
environment, it's hard to think _what_ non-explicit signal there  
could be that a variable is no longer, and never will be, wanted.

Charles


On Aug 2, 2005, at 4:39 PM, Eric Chatonet wrote:

> I was very busy and did not follow accurately this thread.
> I don't speak English very well but I know what global means:  
> global means global :-)
> If you can empty a global, delete it from memory when needed, where  
> is the problem?
> You can use good scripting conventions to be sure that local and  
> global can't shadow.
>