@SSwift: No bug here, Floyd is perfectly right. It actually does exactly the same thing as C does, so relying on C to back up the fact that there's be a bug here is a bit awkward.
The key thing is that there is no such thing as a boolean type in BlitzMax, like in C. False and True are integer constants, and boolean operators actually work on integers, not on true bools.
By example, Not (Not (x)) isn't the same as x in BlitzMax or C, even though in boolean logic it is.
The key thing is that there is no such thing as a boolean type in BlitzMax, like in C. False and True are integer constants, and boolean operators actually work on integers, not on true bools.
By example, Not (Not (x)) isn't the same as x in BlitzMax or C, even though in boolean logic it is.