Boolean vs Int

[trancexx]

I'm getting different return types depending on what I'm running, beta (3.2.13.8 - yeah I know) or stable (3.2.12.1) version.

This code demonstrates the difference:

ConsoleWrite((((1 > 5) & 1) = 1) & @CRLF)

Problem is that I can't find the change to be documented. Is it me or is it not?

Edited November 20, 2008 by trancexx

[PsaltyDS]

I'm getting different return types depending on what I'm running, beta (3.2.13.8 - yeah I know) or stable (3.2.12.1) version.

This code demonstrates the difference:

ConsoleWrite((((1 > 5) & 1) = 1) & @CRLF)

Problem is that I can't find the change to be documented. Is it me or is it not?

The behavior was fixed in 3.2.13.8:

- Fixed #589: Some comparison operators did not return a boolean value.

In 3.2.12.1, (1 > 5) = 0 (not a boolean variant)

Because of that, ((1 > 5) & 1) = 01 (string variant)

When you do "01" = 1, the string is run through Number() and (1 = 1) = True.

After the fix in 3.2.13.8, (1 > 5) = False (Boolean variant, converted to string on display)

Because of that, ((1 > 5) & 1) = False1 (string variant)

When you do "False1" = 1, the string is run through Number() and returns 0 because there are non-numeric characters, so (0 = 1) = False.

Edited November 20, 2008 by PsaltyDS

[trancexx]

The behavior was fixed in 3.2.13.8:

In 3.2.12.1, (1 > 5) = 0 (not a boolean variant)

Because of that, ((1 > 5) & 1) = 01 (string variant)

When you do "01" = 1, the string is run through Number() and (1 = 1) = True.

After the fix in 3.2.13.8, (1 > 5) = False (Boolean variant, converted to string on display)

Because of that, ((1 > 5) & 1) = False1 (string variant)

When you do "False1" = 1, the string is run through Number() and returns 0 because there are non-numeric characters, so (0 = 1) = False.

Ok, thanks for clarifying that.

Does this mean that Is... functions (IsInt(), IsNum()...) will be modified to return True/False in future (near one)?

[PsaltyDS]

Ok, thanks for clarifying that.

Does this mean that Is... functions (IsInt(), IsNum()...) will be modified to return True/False in future (near one)?

As far as I know the functions that are explicitly described as returning 1 or 0 will continue to return an integer type.