Difference in boolean behavior between Number and Float

The documentation says that a 0 is false, anything else is true. A number variable = 0 is false as an if condition, anything else is true so this matches. A float variable = 0.0 is true. Unless Garmin is using some non-standard float format, 0 and integers within fairly large limits can be represented exactly as if they were integers. Changing the if from (x) to (x != 0.0) then flows correctly if x is 0 or non-zero, so treating all floats as true seems like either a documentation bug or a compiler bug.

FlowState over 1 year ago

Yeah, Monkey C has some "interesting" behavior when it comes to boolean logic / expressions / operators.

For example:

var x = null;
if (x) { // compiles and runs fine
    System.println("x is truthy");
} else {
    System.println("x is falsey");
}

var y = 0;
if (y) { // compiles and runs fine
    System.println("y is truthy");
} else {
    System.println("y is falsey");
}

if (x || y) { // either compile-time type check error or run-time type error
    System.println("x || y is truthy");
} else {
    System.println("x || y is falsey");
}

There's also this:

[https://forums.garmin.com/developer/connect-iq/i/bug-reports/strange-behavior-of-logical-operators]

[https://forums.garmin.com/developer/connect-iq/i/bug-reports/int-and-logical]

[https://forums.garmin.com/developer/connect-iq/f/discussion/5513/monkey-c-logical-or-and-and-behave-inconsistently-incorrectly-for-number-types]