Zugg Software :: View topic - [1.33] novel #switch usage with key/val variable

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

This is purely out of curiosity for now

Say I had a variable, testvar
testvar.one = eat
testvar.two = drink
testvar.three = sleep

#LOOPDB @testvar {~(%key~)~ ~{%val~}}

would output
(one) {eat}
(two) {sleep}
(three) {think}
which would be correct syntax for part of a SWITCH...

so... is it possible to do a #SWITCH that would be able to match all the keys and do the values

#SWITCH %1
%exec(#LOOPDB @testvar {~(%key~)~ ~{%val~}})

To get CMUD to use the variable to generate a #SWITCH based on the contents of a variable, which may grow or shrink as the variable changes etc.

I don't actually have a use for it yet, but it could be nifty ;)

Posted: Mon May 14, 2007 10:41 am

No, you can't dynamically generate code this way, because your command there says "if %1 is true then do this %exec function". You'd have to force the #loopdb to run before the #switch command, perhaps by having the loopdb code in an alias that calls the #switch. There are some pretty simple ways to do the same thing with #loopdb though:

#loopdb @testvar {#if (%1=%key) {#exec {%val}}}

should work, and since two keys can't have the same name it shouldn't send more than one command. Adding an #abort command might also cancel the ifs after matching.

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

Urm, Look at the code you just wrote Fang.
#exec {"@testvar."%1}

Tada, I know people don't like to use #Exec but this is certainly faster than a loop.

Posted: Tue May 15, 2007 12:02 am

...You know, concatenation didn't even occur to me. I blame withdrawl symptoms, I've just moved and have no internet at home, so none of my computers with CMUD on are actually useful.

Though it's funny you mention that since someone had a problem with that kind of implicit concat earlier today. It'd probably have to be

#exec {%concat("@testvar.",%1)}