Question an inconsistancy?

[Zxeses]

Code: Select all

  /declare counter global
  /varadd counter 1 
  /echo @counter 

Why does setting and declaring a variable not require the variable signifier, but extracting from the variable does?

wouldnt the following be more consistant:

Code: Select all

  /declare @counter global
  /varadd @counter 1 
  /echo @counter 

Also, why are we using "@" instead of "$" (?)


-Zx

[Plazmic]

The @ is to retrieve the value in the variable
@ as opposed to $ to differenciate user variables from the "EQ variables"

[Zxeses]

I know that @ is the signifier to get data, why isnt it used consistantly like, say, perl or basic, where in every place you have used that variable you use the signifier?


my $perlvar;
++$perlvar;
$perlvar = $this + $that;


I'm pointing this out now in an effort to have it changed now, while these major revisions are happening. Its a lot easier to read and understand when every time you use @myvar, its always @myvar and not sometimes just 'myvar'..

[Curious]

I'll have to second Zxeses ... I can't count the number of times I've typed /varadd $counter 1 and then spent quite some time trying to figure out what's wrong with my script! Or, even worse, is when I finally get use to /varset, and type something like /if n counter==10

[Plazmic]

I really don't want to rewrite the entire basis of the parser right now:
1. receive /command
2. run all params through PMP
3. call appropriate handler for /command

PMP dereferences any @VarName before any /command would see what the variable name was.

Pretend it's like a pointer dereference, without the "&" operator.

[fryfrog]

speaking of the && operator... are we going to see anything like && and/or ||? :)

[wassup]

Personally, I like the @userdefined more than $userdefined exactly for the reason Plazmic said.

@ for user defined variables.
$ for reserved MQ variables
/ for EQ/MQ commands

Makes sense to me and not that much of a stretch to adjust.