Forums Bug Reports if (!anything)

Was the handling of this changed?

Because, if (!1) is true, while if (!$len(1)) is false.

As far as i can see, both are the same.

Greetings.

The difference is that "!1" is a literal string. Like "!help" is a literal string. You can only prepend "!" before a variable (%var), identifier ($me) or an operator (isin). Try the following examples:

//if (!1) { echo -a true $v1 } | else { echo -a false $v1 }
//if (!help == !help) { echo -a true $v1 } | else { echo -a false $v1 }
//if (!$true) { echo -a true $v1 } | else { echo -a false $v1 }
//if (!$true == $false) { echo -a true $v1 } | else { echo -a false $v1 }

I did, but it never triggered like that before.

And if i negate a string, it shouldn't return true.

Because if (string) is true... so if (!string) can't be true too.

//echo $iif(1,1,0) $iif(!1,1,0)

I just edited my post with additional information.

Consider the following, how do you think it should behave?

if (!search* iswm $1-) { /xdccfind $2- }

if "!search*" turns into "$false" then it wouldn't be "!search" anymore.

Well yeah i see what you mean, haven't thought of that.

Anyway this is a bit different from what i was looking for, but i understand what you mean and how it is triggered there. Even if you would negotiate iswm with !iswm.

So $iif(!$(1),1,0) will solve this for me by now.

It was a long week.

Good night.

I just can't imagine why you would manually hardcode your IF expression with a negated number if you could just as easily type $false or 0 or get rid of the IF all together.

Use a variable that has some meaning, instead of the naked number 1.

It has nothing to do with that, i just came up with it during a mistake on a script and didn't saw the "string" possibility.

Just because of other languages where numbers alone are always triggered as numbers even with the leading exclamation mark.

So... notice it as a mistake.