Thanks Andre and Malte. Indeed the culprit was "check variables by
default." I don't recall having checked it. I was testing Galaxy
for a while in 2.6.1... seems unlikely but perhaps that had to do
with it? At any rate... great list. Much appreciated.
Eric, I'll try to get into this habit if it's considered good form,
but since I already use the gGlobal convention, I can identify local
variables easily enough. If there's no g in front, it's local, and
by context it's a variable, no? Where does it become problematic in
interpreting undeclared locals?
Mark
On Oct 24, 2006, at 2:07 AM, Eric Chatonet wrote:
Hi all,
I take the opportunity to say how useful is to set explicit
variables to true.
It's not only good practice but will track for you misspellings and
errors :-)
When explicit variables are set to true, all local variables must
be declared or a message as the one Mark reported will show up:
on MyStuff
local tData,tFlag
-----
put the optionKey is down into tFlag
put fld "Data" into tData
You get the idea.
In addition, for those who always work declaring all variables,
it's a bit bothering to inspect other people scripts where they are
not declared ;-)
Le 24 oct. 06 à 06:50, Mark Swindell a écrit :
Over the past couple days I've been encountering a frustrating
behavior in that when I go to save a stack script, I'm greeted
with the following error message:
Type Chunk: can't create a variable with that name
(explicitVariables?)
Object FF Stack
Line put "multiplication addition division subtraction" into
theCardsToChange
Hint theCardsToChange
_______________________________________________
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
