You said "...you said it's easy to devise a new variable name and scan the script to make sure it's really not being used yet. Isn't it even easier not to have to do that?"
It depends on the situation. It's faster to do a search than to type "my" 50 times. Sometimes you could recognize that a variable has or hasn't been used before, and variables as long as your example of "$lineIuseHereAndOnlyHere" aren't necessary to make sure you know where belong and avoid accidental reuse, even in a 3000 line program. I know, because I wrote such a program.
I'm not trying to talk anyone into using more globals. I just posted VarSructor, and if you have no use for it at the moment because you don't have to maintain a script that might have globals that you want to locate in the easiest way possible (seems like my detractors would be interested in that so they could refactor it), and if you don't have to reset variables in someone else's script so you could safely loop it without a major rewrite, then don't use the script.
