Zugg Software :: View topic

Newbie Joined: 09 Jan 2005 Posts: 5

I'm trying to do something like this.

#forall (@list) {
#var value @%i_value
#if (@value > X) {#sa Hi}
}

I can use @%1_value in triggers, but i can't use %i in a #forall it
just ends up becoming silly.

Anyhoo, if someone has an idea of what i'm wanting to do and knows
how to solve it, feel free to help me out.

**EDIT**
Nevermind, i figured out a way. Ugly, but works =)

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

This was an interesting problem for me

Apprentice Joined: 26 Oct 2004 Posts: 108

here's a solution I've used for a poker game of mine that uses variable-variables..
WhereI've done this to test..

#var test {test1|test2|test3}
#forall @test {#if (%eval(@%eval(%i+"_value")) == "1") {#echo yay}}

Meaning I eliminated the whole #var value thingie and just did the if statement directly.

You could instead of '== "1"' put your '> X' ..

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

%i_value is undefined. To get %i with _value appended, you have to specify how much of the string the % refers to.

#forall (@list) {
#var value @%{i}_value
#if (@value > X) {#sa Hi}
}

Apprentice Joined: 26 Oct 2004 Posts: 108

Lightbulb, Ah... well for some reason, zMUD is selective as to when that is applicable for me. Even if it's the same code, sometimes it will not just compute the same at diff times.

Such things I tend to avoid afterwards... and one such is the "selective-expansion" with brackets thus I had totally forgotten about it.

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

Sorry about the other reply but I am having tech problems.

Anyways I attempted this proble from alot of different angles and it seems that the problem is using %i with _

I tried the one Lightbulb suggested but it did not work.

I was able to come up with a work around for you though.

Posted: Sun Jan 09, 2005 6:57 am

This is how it should be done, period.

#forall @list {#if (@{%{i}_value} > X) {#sa Hi}

Wink

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

Do not use PEGA'S
It does not work in the future he should probably test it first.

Posted: Sun Jan 09, 2005 10:02 am

I tested it, and it works for me. If it does not work for you, my guess is you did something wrong in another part of your script.

Cool

Posted: Sun Jan 09, 2005 10:29 am

Unexpected results? I think megamog75 is encountering a nesting problem. You have to watch for that.

%i and @{%{i}_value}

or%%i and @{%{%i}_value}

Apprentice Joined: 26 Oct 2004 Posts: 108

Executed:
#var test {test1|test2|test3}
#var test2_value 2
#forall @test {#echo @%{i}_value}

Result:

Posted: Sun Jan 09, 2005 2:40 pm

Apprentice Joined: 26 Oct 2004 Posts: 108

quoting my own words and only adding "Hope that helps" is in no way a satisfactory reply.

The %eval stuff is not "valid" since I corrected myself with the last sentence you quoted and recognized that there is an alternative, only that it has not worked for me previously all that well.

And I also said in the first quote you've pasted that zMUD is buggy in that sense sometimes, so I am once again pointing it out and fully aware of it. So the meaning behind your post eludes me. Please make some more useful posts than quoting alot of stuff in a miss-guided order.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

As lightbulb stated %{i}_value is the way to do it. It is not buggy {}'s are for grouping they do not perform expansion or evaluation.

But on another note Have you tried using a data record? From this small portion of script it might suit a better purpose.

Posted: Mon Jan 10, 2005 5:20 am

The additional { }'s were meant to standardize the evaluation for indirect access of variables.

In this case, it was for the set of @{%{i}_value} variables, while @list is in effect a list of pointer offsets.

misterbalrog lamented about zMUD being selective as to when expansion was applicable to him.

and using the @%{i}_value variable as such can be ambiguous if gone unchecked.

I think that the @{%{i}_value} is more flexible than a data record, but a data record may suffice depending on the situation. *shrug*

Smile

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

Pega, no disrespect but the reason I said not to use you script was because you left out the end } to inclose your script.

I didn't have it wrong, it simply did not work.

I tested the others and they worked pretty good for me, however when I was working the problem I tried them and they did not work lending to the statment that sometimes zmud does something right about 1 million times and then once just messes up.

Posted: Mon Jan 10, 2005 11:35 am

Posted: Mon Jan 10, 2005 11:16 pm

Tell you what, I have not been scripting on zMUD that much in recent years, and the problems that I saw several years ago are not applicable now. Perhaps the extra braces for variable representation are unnecessary or they may apply in other areas.

My bad.

As far as I can see at this time,

@%{i}_value and @{%{i}_value}

are in effect identical and the braces are redundant.

Best regards

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Well I suggested a data record because from the looks of it he is just trying to use linked variables which can lead to multiple variables and then trying to remember them all while a data record would group them into one var which could be looped with a #LOOPDB

instead of having
this={one|two|three|four}
one_value=1
two_value=4
.....

you would have something like this

Values.one=1
Values.two=2

It could be just me but I find it easier when the variables are grouped :P

Apprentice Joined: 29 Jul 2002 Posts: 105

I was playing with something similair with #forall's and one thing I did notice. %eval solves some problems, but also isn't needed other times. The major difference was where things appeared. Command line, in an alias, in a trigger, in a alias used by a trigger. They didn't all play nicely together.