Zugg Software :: View topic

Posted: Wed Jun 10, 2009 8:05 pm

I think I found a few more local varible parsing errors when used with #var

1) From blank session paste following code

Posted: Thu Jun 11, 2009 12:15 am

This is actually the correct operation of the #VAR command with local variables. When you reference the local variable directly (like with {$var} or $var in your first two examples), you are modifying the actual local variable itself and not the variable pointed to by the contents of the local variable (indirect assignment). The only way to do indirect assignment with #VAR and local variables is using a function, like in your third example. Using something like %string($var) also works.

Indirect variable assignment like this is a very advanced topic and it's not something I expect novice scripters to be using. Advanced scripters just need to learn the specific syntax for doing it. For novice scripters, then expect:

#VAR $local value

to assign "value" to the local variable...they don't understand the concept of indirect variable assignment. The issue only arises at all because local variables have a simplified syntax where you *always* use the $ in front of the variable name. With normal CMUD variables, the @ is only used to reference the value of a variable rather than the name of the variable itself. Local variables don't have that distinction, so it's sometimes tricky to mix local variables into a syntax that was created to support normal variables.