Actually, to delete a global from the message box you need:
global <globalName>; delete global <globalName>
I guess it is the same as having to refer to the global (initialise
it?) in a script before using it.
At 7:36 PM -0500 1/8/05, [EMAIL PROTECTED] wrote:
Now hold on a minute; I did remember a time a version back when I set
a global when I should have set a local, and the global wouldn't go
away, I couldn't recreate as a local, even though I used 'delete'
from the msg box. It insisted on being a global. I had to quite rev
to continue...
sqb
On 8/1/05 2:28 AM, "Mark Wieder" <[EMAIL PROTECTED]> wrote:
Global variables are persistent in memory, even when they've been
purged. Once you have declared a global variable, even if you have
deleted the line of code that declared it, you're stuck with it.
Well, yes, but that's because you didn't explicitly delete it, which you can
do with:
delete global <globalName>
Ken Ray
--
Michael J. Lew
Senior Lecturer
Department of Pharmacology
The University of Melbourne
Parkville 3010
Victoria
Australia
Phone +613 8344 8304
**
New email address: [EMAIL PROTECTED]
**
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
