Forums Bug Reports $calc() and variable assignments

I have two questions:

A $calc() without an argument seems to halt the script processing, instead of returning $null or throw an error in the status window. Is this intented?

I also wonder why C-style variable assignments (%var = value) does not work on the command line.

not sure on item 1.
but for 2.. its //set %variable value

remember, from the command line, the interpreter needs 2 forward slashes to do its thing
and mirc uses /set its not exactly like c code

I know /set works, but since the %var = value statement is some sort of macro for /set, I don't see a reason for it not to work.
Try the following and you'll know what I mean:



Using double slashes or not has nothing to do with it either, try:



This will stop executing when it hits %i = 5, which leads to not producing the /echo.

You probably already know this, but the format for setting a variable using the /set command is /set %variable <value>
This sets a global variable.
Using the /var command the format is /var %variable = <value>
This sets a local variable.

While I have seen variables set using the format that you have used in your command line sequence, the only time I've seen it done is in a script format, not in a direct command line.

I tested this out, and while your command line code does work as you say, if you put in the var before the %i after the first pipe, then it does give the proper output.

I suspect that using %variable = <value> without the var command will only work in a scripted situation, but not in a direct command line.

That's his point.

This was the point of my post, I wonder why %var = value does not work on the command line, while in remote it does. I use these kind of statements in my scripts, and I find it inconvenient that it does not work for the command line, when I want to write something quick in the editbox.

Also note that /var is NOT the same as %var = value (rather a collection of /set -l). There is also a noticable speed difference when using /var comparred to /set in loops.

%var = value doesn't work in command line because any command that starts with a variable/identifier in the command line is blocked for security reasons ($decode stuff). Unfortunately, at the moment, mirc can't distinguish between a variable being a command name or part of a variable assignment.

That's too bad. I hope Khaled will make an option to unlock these restrictions (being disabled by default as $decode, of course) or in some other way letting you set the security level.