Zugg Software :: View topic

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

I am trying to revise and old script and I am not sure if I have the correct syntax anymore for CMUD.

#IF (%match( @input.1, ~[|~])) {
#VARIABLE emph @input.1

In the above the variable emph isn't being populated. If I do a #SHOW @input.1 is gives the correct values. Help please.

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

The problem is your %match() pattern. You're testing if @input.1 = "[|]", rather than @input.1 = "[" or "]". This causes the #VARIABLE command to never fire.

To fix, you need {} and perhaps will need "" around all of it

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Okay.. Here is the issue. The mud I am playing will let you have emphasis in your communication.

say (with a smile) You can't do that.
Output: You say, with a smile, "You can't do that."

Now the mud parses the (). I want to capture those also into the variable.

Beginning of script:
#var channel %1
#var input %params(2)

when I show the @input variable it shows: with a smile You can't do that.

Now I know that I could put a ~ in front of the () to capture them, but I don't want to do that. Is there any way to capture the ()?

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

Go look at the @input variable in the Package Editor. The () are already captured. The reason you don't see them in the show is because they are being evaluated as an expression. The only way to reveal the () in the show is to use %quote(), which puts a ~ in front of the ().

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Matt when I look at the @input variable in the editor it shows: with a smile You can't do that.
The () are not captured. Do you have something disabled?

if I put the ~ in front of the () with my script like so:
stutter say ~(while smiling~) You can't do that.

It will capture the () in the @input variable. I don't want to have to put the ~ in front of them.

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

If you don't want to use ~ then use "":

stutter "(while smiling) You can't do that."

The issue is that CMud uses naked ()--that is, any parentheses that are not quoted or inside double-quotes--to denote expression evaluation. It's just like in a trigger where you have to quote parentheses when you want to match them because triggers use () to capture subpatterns into the %1...%99 variables.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

I do know that information. I was just wondering if there was a way around it. I just didn't want to use the ~. Let me think about the using quotes instead.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Okay. I decided to use quotes to capture the () in the variable..
Now this is what I could have captured:

(nervously) I am not sure if I want to do that.
OR
(while smiling) I am not sure if I want to do that.

Here is what I want to do: I want to capture anything inside the parenthesis, including them and put into another variable and leave the rest in the input variable.

I've tried a few ways but I am having difficulty finding an easy way to do it..
Any ideas?

Posted: Sun Sep 12, 2010 11:36 pm

Why not just use the subpattern capturing functionality of %match itself? For example, assuming @input was "(nervously) I am not sure if I want to do that." then this:

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

I used the %match function, but I don't want it to return a 1, because it sends it to the mud. Is there a way not to do that.

Here is some of the code:

Posted: Mon Sep 13, 2010 6:36 am

Whenever a function returns a value you don't want to pass on just assign the result to a local variable:

Wizard Joined: 22 Mar 2007 Posts: 2320

Alternatively, use the #CALL command: #CALL %match(...
The problem with your code was that you were starting a command line with a % function. You should never do that. This was frequently done in Zmud, but you should avoid this practice in Cmud. Starting a command line with a function can lead to many problems, and even break your code. Instead of starting a command line with a function, start it with the appropriate command--some of the choices are: #CALL, #SEND, #EXEC, #SAY. (Don't use #NOOP--this is denigrated in Cmud).