/newif Parse bug?

LordGiddion · Post by **LordGiddion** » Sat Apr 10, 2004 9:01 pm

This works and appears to function correctly

/newif !@DoArchery  {

and so does this

Code: Select all

/newif (@DoArchery==0) && (@Combatstatus) {

but this fails and comes back as couldn't parse && (0) (note execution doesn't end it contnues)

Code: Select all

/newif (!@DoArchery) && (@Combatstatus) {

ml2517 · Post by **ml2517** » Sat Apr 10, 2004 9:04 pm

Not at a pc right now but try pressing them together and surrounding them.

Code: Select all

/newif ((!@DoArchery)&&(@Combatstatus)) {

LordGiddion · Post by **LordGiddion** » Sat Apr 10, 2004 9:19 pm

Interesting

Code: Select all

/newif (!@DoArchery)&&(@Combatstatus) {

Fails and the error is couldn't parse "&(0) {" notice the the error turns from && to &

but

Code: Select all

/newif ((!@DoArchery)&&(@Combatstatus)) {

Works seemingly 100% correct

Lax · Post by **Lax** » Sat Apr 10, 2004 11:30 pm

I'll look into that, ! might be killing an extra part or something

Lax · Post by **Lax** » Sat Apr 10, 2004 11:32 pm

oh and, this isnt a /newif bug it has nothing to do with /newif. It has to do with Calculate. *repeats himself a few more times* . . /echo ${Math.Calc[your conditions]} will tell you the same thing its telling /newif.

/newif just calculates your conditions.

anyway I'll get on that tomorrow

LordGiddion · Post by **LordGiddion** » Sun Apr 11, 2004 7:50 am

Sorry Lax, I've heard you say the Calculate vs/ Newif thing a few times but I thought you were activly pounding at both so I figured I just say where I saw it rather then confusing a bunch of people by calling the post calculate formating and having /newif examples.

Lax · Post by **Lax** » Tue Apr 13, 2004 6:57 am

Okay, did some testing and found... the problem has to do with your spaces!
"Couldn't parse <whatever>" is what is said when you try to execute a command that doesnt exist.

/newif (1) && (1) /echo hi
Couldn't parse '&& (1) /echo hi'

/newif ((1) && (1)) /echo hi
[MQ2] hi

So if you're going to use spaces, you do need to use parentheses around the whole thing

We could require parentheses in /newif... hmm..

So it was actually a /newif (and the same thing would happen with /if actually) issue. But, I did find an issue with ! during my testing.

${Math.Calc[!0&&1]} => 0 (incorrect)
${Math.Calc[(!0)&&(1)]} => 1 (correct)

ml2517 · Post by **ml2517** » Tue Apr 13, 2004 9:01 am

Just require parenthesis and work on real problems