Unexpected behavior of = equals operator conditionals

[water]

... but there is no rule for when strings are treated as numbers.

It's in this sentence (taken from the help file as posted in #3): "If a string is used as a number ..."

If you do a comparison using "=" and one operand is a number then the second needs to be a number too. If it is a string "an implicit call to Number() function is done"

[mwhidden]

I must respectfully disagree that the only interpretation is that the 2nd needs to be a number too. It is at least conceivable that it could have been the other way -- that when one states if("abc" = 1) that the 1 is converted to "1" as happens with the & operator, or even that it were just generally the case that strings and numbers are never (except in pathological cases) equal (ala C/C++ comparing a char* to an int with proper typecasts).  Therefore, I think it is worth documenting that the authors of AutoIt chose that when comparing a number to a string that the string becomes a number, and not vice versa. 

Because = so naturally applies both to strings and numbers, (while, on the other hand, +, -, * are clearly numeric), it is ambigiuous in the documentation of which type takes precedence in a comparison. In fact, numbers are preferred, but the only way to learn this is to try it in code.

[water]

I support every effort to make the documentation as clear as possible. I see you have already posted on the help file thread. Let's see what Guinness thinks about the issue.

[AZJIO]

mwhidden,

 I will dig up a couple of links

'?do=embed' frameborder='0' data-embedContent>>

[mwhidden]

@AZJIO,

Thank you for the additional references!

-mwhidden