Bob, et al:
A couple of follow up thoughts:
And script local variables cannot be accidentally or purposely read
or changed by scripts in other stacks or other objects.
This may not mean much if you are developing end user applications;
however if you are building libraries that may be used
Oh I see how that works. That makes sense for distributed developer
tools. You are preventing unintended changes to your internal
variables from the the outside world while providing a mechanism for
accessing them if needed. I never understood Script Local variables
until now.
Bob
The big thing about globals for me, even more than their scope, is
their persistence. I can declare a global and check it's current value
in the message box without any script even running. They are the only
way to do environment variables, where the state of various things can
be
Bob, et al:
I would only use
script local variables for temporary variables that only need to live
while the script runs
The Rev Dictionary says:
The difference between a script local variable and a global variable
is that a script local variable can only be used in the handlers of
one
, hide
everthing you don't want to see. It will be available
in the future if you update the stack.
However, I don't know how to show globals assigned
ONLY to the current stack. Does anybody know ?
If you want the scripts, catch me off-list ..
-Francis
Nothing should ever be done
Francis Nugent Dixon wrote:
However, I don't know how to show globals assigned
ONLY to the current stack. Does anybody know ?
I'm not sure what you mean. Globals are global in scope, available to
any script with a matching global declaration.
--
Richard Gaskin
Fourth World
Revolution
On 12/10/08 8:24 AM, Richard Gaskin [EMAIL PROTECTED] wrote:
Francis Nugent Dixon wrote:
However, I don't know how to show globals assigned
ONLY to the current stack. Does anybody know ?
I'm not sure what you mean. Globals are global in scope, available to
any script with a matching
Francis Nugent Dixon wrote:
However, I don't know how to show globals assigned
ONLY to the current stack. Does anybody know ?
Richard Gaskin wrote:
I'm not sure what you mean. Globals are global in scope, available to
any script with a matching global declaration.
Yes, but why would
On Dec 10, 2008, at 12:54 PM, Fred moyer wrote:
Francis Nugent Dixon wrote:
However, I don't know how to show globals assigned
ONLY to the current stack. Does anybody know ?
Richard Gaskin wrote:
I'm not sure what you mean. Globals are global in scope, available
to
any script
Hi from Paris,
Sorry Richard, my explanation was vague.
Launch a standalone, of any single stack,
and look at the global variables as I do,
and you see only those currently assigned
to the stack (obviously).
In the IDE, open several stacks at once,
switching from one stack to another, and
in
Francis Nugent Dixon wrote:
In the IDE, open several stacks at once,
switching from one stack to another, and
in any of the stacks, you see the total list
of globals defined by all current stacks, and
you don't know which globals belong to which
stack.
It seems appropriate that the Message Box
if
return the var of stack where
end setValue
function getValue var, where
return the var of stack where
end getValue
-- end copy -
On 12/10/08 11:54 AM, Fred moyer [EMAIL PROTECTED] wrote:
Francis Nugent Dixon wrote:
However, I don't know how to show globals assigned
ONLY
Hi everyone. Am I the only one for whom the script editor on 3.0 is
glacially slow? It is almost impossible at times to code, especially
when I have lots of huge globals loaded.
For that matter, in Preferences, it seems that checking or unchecking
Show Globals in the Script Editor area
when I have lots of huge globals loaded.
For that matter, in Preferences, it seems that checking or unchecking
Show Globals in the Script Editor area makes no difference. I still
see all of my globals (as well as $User and other $ variables)
listed. Simply comparing 2 variables if they start
more, or delete them entirely.
For that matter, in Preferences, it seems that checking or unchecking
Show Globals in the Script Editor area makes no difference. I still
see all of my globals (as well as $User and other $ variables) listed.
Simply comparing 2 variables if they start with say
The script editor is just fine as long as you don't need to debug anything
complex. Once you've got more than a few variables, and particularly if
these include multidimensional arrays it bogs down horribly. It needs some
attention I reckon!
Terry...
On 10/12/08 4:03 PM, J. Landman Gay [EMAIL
16 matches
Mail list logo
