 |
struesdell
Beginner
Joined: 30 Nov 2006
Posts: 11
Location: Seattle, WA, USA
|
 Posted: Tue Dec 26, 2006 8:55 pm
[1.24] Invalid Local Variable?
|
I've had this happen a bunch, and I haven't figured out why yet.
I'll create a new trigger, such as...
has a partially damaged ($side:%w) ($limb:%w).
then, I'll try to use $side in the script.
#var %concat($side,$limb) damaged
Only to have the syntax checker report that
"Invalid Local Variable side at row 0 col 13"
Any idea what's wrong? It's working fine for $limb, and I don't see any differences between them. Is $side a reserved name? I've had this happen with $h and $m before, as well as $s. |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Tue Dec 26, 2006 11:48 pm
|
I've seen the same thing happen. Sometimes when local variables are declared implicitly (i.e., not defined with #LOCAL), CMUD gives you an error when it shouldn't. I'm sure it will be remedied soon.
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Wed Dec 27, 2006 8:26 pm
|
Never had it happen in localvars defined in the trigger pattern (thankfully) but I have had it happen with $localvar=value. Bit easier to remedy with the #local command in that situation.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jan 17, 2007 10:17 pm
|
The problem is that the #VAR command is currently not handling indirect variable assignment at all. This is on the bug list.
|
|
|
|
|
|
|
|
