Extensions have boolean logic limitations?

[Carl Lydon]

Hi,

In an extension, if I try something like:

if (x==1 or y==1){
//do something
}

The script won't load. If I get rid of the "or" and do a nested "if" statement, it works fine. Is this a known limitation?

[BigFIsh]

use || instead of or, same with and = &&

[ptdgames]

Also, get into the habit of doing this:

if ( (x==1) || (y==1) ) {
// do something
}

The extra () sets will make sure the compiler behaves exactly the way you want.

[duncanhall]

I would advise the exact opposite of what ptd suggests.

The compiler is more than happy to recognise (x==1 || x==2) as two seperate conditionals, and the added parenthesis just make it harder to spot exactly what is being evaluated. I would only really include the nested parenthesis when you have multiple evaluations in each conditional.

eg:

if (( x > 3 && x < 10 ) || (x > 20 && x < 30))

[Carl Lydon]

Thanks for all the advice. The main thing was that my Flash compiler always recognized "and"..."or", but that Smartfox extensions might not. I'll be in the habit now of always using || or &&