Zugg Software :: View topic - How to send captured-text to a variable without phrasing?

Beginner Joined: 03 Apr 2006 Posts: 12

Is there a way to send some text captured by a certain pattern straight to a variable before phased by Cmud/zmud?

e.g.
trigger {^the wolf is traped by a weapon like (%*)} {#va weapon %1}

if the text is "()" which match the pattern (%*) in the trigger, how to #va it straight to the variable @weapon without phrased by cmud/zmud?

I wish there an option added to #va/=/#additem/@variable etc. to switch on/off phrasing when we use the #va/@variable command to put-in or get-out a certain value,is it there?

Posted: Fri Apr 07, 2006 6:32 pm

In CMUD this shouldn't be a problem. CMUD won't parse or expand the %1 coming from triggers. This is due to a difference in how the compiled parser works compared to the old zMUD parser.

In zMUD, the %1 variable was done first as a string substitution. Then the resulting #VAR command was executed. This caused expansion of the %1 contents.

In CMUD, %1 is treated as an "argument" (like in a function or method) and is replaced when the #VAR command itself is executed. It pulls the argument from the current runtime stack and performs the variable assignment. Since the trigger variables like %1 are strings, there is no expansion or evaluation of %1 when it is assigned.

This should make triggers work more like expected.

In zMUD to accomplish this, you can try putting quotes around the %1 like

{#va weapon "%1"}

and that should prevent the parsing. But this shouldn't be necessary in CMUD.

Beginner Joined: 03 Apr 2006 Posts: 12

that's ok,zugg,thanks for your replication!

but a more question about parse, is there a way in cmud or zmud to use @weapon or %item(@weapon,n) straightly get-out the value of variable "weapon" or the nth item of "weapon" without parsing it(the value)?

I thought it is powerful to make cmud/zmud's command&function to set/ get-out the very text(or anything else) which captured by a trigger straighly to/from a variable without parsing, this can make it more suitable for any cases whether the text captured by a trigger contains a wildcard or not, isn't it?

Posted: Sat Apr 08, 2006 4:51 pm

wwwfisher, I'm not sure I understand what you're asking... Are you trying to find an easy way to access ith item in a list?

Beginner Joined: 03 Apr 2006 Posts: 12

Not exactly, I want a way to prevent the "@" or "%item(,)" etc. operater prasing the value in variable or itemlist when getting it out, only get-out it as what it(the value,wheter it contains a wildcard or not) is.

Sorry for my poor english.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

doesn't %expand() do this already? I know you can nuke the parser down to just <> and [], but I dunno if functions or variables are handled before this step or not.

Beginner Joined: 03 Apr 2006 Posts: 12

whether you use %expand() or <> or [], once you use "@" or %item(,) operater to get-out the value of a variable or an itemlist, the default operation of "@" or %item performs phrasing it(the value).

I want a way to prevent the operater prasing the value when it was got-out, as default,the operater performs prasing ation on it when it was got out.

is there a way to do so?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

please read the helpfile, wwwfisher. %expand() does exactly what you want. If not, make a new topic and show a code example of what you're trying to do.

Beginner Joined: 03 Apr 2006 Posts: 12

Sorry for my poor english, it was too bad to be understood! Sad

I have read zmud's help, and get some knowledge that %expand() or <> or [] performs such action as below: whether to return the "@variable" format as a string or treat it as an variable and reurn the value of it).Am I right?

but what I talked is the VALUE of a variable or the nth item in an itemlist, I wish there's a way to prevent the command to prase the value (not the format of varialbe-name/text) when we got it out use a command or function.

As the {#va weapon "%1"} which used "" to stop #var prasing the value in %1 and straightly assigns it into an variable. Can we use {@"weapon"} to get-out the value stored in variable weapon and prevent @ prasing it(the value of %1 in this example)? the answer is NO. that's what I want.

Maybe there's no answer for this,unless zuggsoft makes an upgrade of the commands and functions which manipulate values in/out a variable or an itemlist. OR CMUD already does so! As zugg talked above. Rolling Eyes

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Beginner Joined: 03 Apr 2006 Posts: 12

ok,try to test below, as someone else early posted:

#va test %char(191)
#va test1 %char(191)zmud
#sh @test
you will get
@test=¿
#sh @test1
can you get {@test1=¿zmud}?

I think the @ operater do prasing on "¿zmud", and makes us not got the expected value, I want a way to prevent @ do the prasing,only get the value "¿zmud" out.

am I right?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

The following code produces the following results. I'm not sure why 191 produces different output, however. Regardless of how I worked with it, there was no way to get %char(191) to display the hispanic opening question mark when concatenated to anything else (including whitespace), so I'm guessing some sort of bug or legacy meaning for that character. Not sure if a bug would be possible without also affecting more than just that one character, however.

Beginner Joined: 03 Apr 2006 Posts: 12

I thought the #va command here or %char function performs a prasing action on the value which got out by @ or % operater, In such cases, switch off parsing(within those commands and functions which manipulate values in/out a variable or an itemlist) maybe more suitable for us to get the very thing we want.

would this be applied in CMUD?
Or an upgrade for zmud in future?
Rolling Eyes

Posted: Mon Apr 10, 2006 5:16 pm

Also, as people have said, the %expand function will do this if you use a 1 for the argument.

#va test1 %char(191)zmud
#show %expand(@test1,1)

Normal variable expansion performs recursive expansion of the value. Using the %expand function you can control exactly how many recursions are performs. Using a 1 as the argument to expand performs the initial expansion of @test1 to it's value but then stops and doesn't expand the value.

Beginner Joined: 03 Apr 2006 Posts: 12

oh? let's try it in zmud

#va test1 %char(191)zmud
#show %expand(@test1,1)

anybody got the result {@test1=¿zmud}?
I do not got it!

for %expand(), I have read zmud's help, and get some knowledge that %expand() or <> or [] performs such action as below: whether to return the "@variable" format as a string or treat it as an variable and reurn the value of it.

and in the above example, there's no "@variable" format contained in the returned value "úmud", the %expand(@test1,1) dosen't fire.

if we use

{#va test %char(191)
#va test1 "@testzmud"
#show %expand(@test1,-1)}

we will get "@testzmud" , and if we use

#show %expand(@test1,1)

"@test" in "@testzmud" which we got using{#show %expand(@test1,-1)} will be treated as a variable, and %expand will fire 1time and return the value in @test instead(in theory according to %expand function's explanation). but this not happened, the %expand function do nothing again! the "@testzmud" was traited as a variable by the name of "testzmud",bug and bugs again?! Evil or Very Mad

Back to our topics, %expand() function performs action on "@variable" format, not the phrasing of the value returned (here in zugg's example, I thought the phrasing performs action on "¿zmud" and make us get an unexpected result "úmud"). Am I right?

zugg tested it in CMUD? Rolling Eyes

if it is, that's would be GREAT!!!!!!!!!!!! Very Happy

stick to my topic please
I thought the @/% operater do phrasing on "¿zmud", and makes us got the unexpected value "úmud", I want a way to prevent @/% doing the phrase, only get-out the value "¿zmud" as it is. IS IT THERE? Rolling Eyes

If it's a bug, Please fix it and make it more robust!

SubAdmin Joined: 18 Nov 2001 Posts: 5182

To be totally clear %expand is behaving exactly as advertised.

A small series of tests for you to preform with zMud v 7.21
#SHOW {%char(191)zmud}
Displays "úmud".
#VAR test {%char(191)}
Sets the variable test to "¿" confirmed in the settings editor.
#VAR test1 "@testzmud"
Sets the variable test1 to "@testzmud" confirmed in the settings editor.
#SHOW @test1
Displays a blank line, due to @testzmud being null, recursive expansion.
#SHOW %expand(@test1,-1)
Displays "@test1", no <> or [] notation is present in the string "@test1".
#SHOW %expand(@test1,1)
Displays "@testzmud" again correct expanded 1 step so the value of of the variable test1 was displayed.
#VAR @test1 "@{test}zmud"
Sets the variable test1 to "@{test}zmud" confirmed in the settings editor.
#SHOW @test1
Displays "úmud" due to full expansion again.

Now here is the real pickler problem that your actually having; and I believe this is a Windows thing.
#LOOP 255 {#SHOWP %rightback("00%i",3) %char(%i) '%char(191)%char(%i)'%char(32);#IF (%mod(%i,8)=0) {#SHOW {}}};#SHOW {}
Gives a lovely output of:

Adept Joined: 04 Feb 2005 Posts: 246

Oops, posted before noticing a second page.... What Vijilante said... Smile

Beginner Joined: 03 Apr 2006 Posts: 12

oh, thanks for your great post,Vijilante.

but there's one point I disagree with you, as you said

Posted: Wed Apr 12, 2006 1:22 am

Any "fix" to this will only be applied to CMUD. As mentioned in the other post about Variables Types, CMUD handles parsing in a completely different way that should solve this problem. No changes are planned for zMUD.

Beginner Joined: 03 Apr 2006 Posts: 12

Posted: Wed Apr 12, 2006 1:52 am

Not likely, view the ETA thread. It has just been updated and points to end of April or later.