Zugg Software :: View topic - [2.01] Cross-Module Variable Referencing

Magician Joined: 13 Oct 2000 Posts: 463

I have two modules in a package. It's pretty simple... one trigger, one alias, and two variables.

I'm a bit puzzled though why it's not working. It's simple and straightforward.

Every time I type the alias 'bbread', the number should increment by one, so that next time I type the command, it will show me the next post on the same board. Unfortunately, it does not do this, and I can't figure out why. Also, classes named 'BB' appear in other modules.

Either I'm doing something wrong, or 'private' modules aren't working properly. Here is the XML to the two modules (I have them in one package named 'BB', but I'm not certain that should change anything):

<module name="BB">
<uid>{ACECFB4D-0B61-40D5-B58C-CBBB0CF0A3D7}</uid> <var name="bbnext" type="String" default="u" usedef="true" saved="false" id="2">99</var>
<var name="bbboard" type="String" id="4">1</var>
</module>

<module name="Interface" id="5">
<uid>{B5D3D248-E333-4AEA-8F76-BCB0C7EE2D2C}</uid> <alias name="bbread" id="1">
<value>
#IF ($post > 0) {#VAR bbnext {$post} _nodef {//BB}}
#SEND {+bbread @//BB/bbboard/@//BB/bbnext}
</value>
<arglist>post</arglist>
</alias>
<trigger priority="30" case="true" id="3">
<pattern>^Message: (%d)/(%d)</pattern>
<value>
#VAR bbboard {%1} _nodef {//BB}
#VAR bbnext {%eval(%2+1)} _nodef {//BB}
</value>
</trigger>
</module>

The alias 'bbread' takes one argument, which lets you specify a different post than the default next one.

The trigger finds lines that look like "Message: 3/14 ...". 3 would be the board, and 14 would be the post. It adds one to the post number, and saves that into @bbnext.

@bbnext and @bbboard are stored in the private BB module. This is the part that appears to be broken (the fact that it is private). It's not strictly NECESSARY for private variables, but I'd really like to have this work, since I'm not a fan of global namespace pollution.

Posted: Mon Aug 27, 2007 7:19 pm

You shouldn't be using the Class argument of #VAR to specify the module name. You are making this too hard on yourself. Also, in your #SEND command, you need some {} around the variable names to avoid confusing the parser. Here is the correct syntax for your alias:

Magician Joined: 13 Oct 2000 Posts: 463

That works just fine. So... does that mean #VAR {var} {value} {default} {//module/class} syntax is broken? Should that be deprecated or abandoned?

Posted: Mon Aug 27, 2007 7:34 pm

I think the //module/class in the #VAR command is broken, and I've added it to my bug list. But it's so much easier to read the newer syntax that I'd avoid using #VAR for complicated stuff like this.

Also, calling #VAR is slower than using the var=value syntax since the var=value syntax is built directly into the compiler, where as #VAR has the overhead of a command call.

Magician Joined: 13 Oct 2000 Posts: 463

Hrm. Can you dereference variable names using that syntax? What's the equivalent to this?

#VAR @Foo {value} {} {//class/path}

This does not compile, for obvious reasons:

//class/path/@Foo = value

Is there a workaround?

Apprentice Joined: 12 Jul 2004 Posts: 190 Location: Canada

There's probably an easier way, but you can always do #EXEC %concat("//class/path/",@Foo." = value") to do this.

I'm not too well-versed in the {} syntaxes in CMud yet (I'm still stuck in my old zScripting mindset)... but have you tried something like:
//class/path/{@Foo} = value ?? I haven't tried it, but it might work.

Posted: Wed Aug 29, 2007 7:54 pm

I believe just putting () around the expression will do it. For example:

#VAR (@Foo) {value}

I don't think you can do indirect assignment with the varname=value syntax.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

For LOCAL variables it makes you use %eval() () isn't enough I haven't tried it with normal variables.