I wasn't sure about this. The examples on that page were not immediately clear to me, and I didn't have time to spend on them, but, we do now have both And() and Or() functions... Are these the same as referenced on that page? If yes, that just leaves XOR, and I have no idea what that means, and a very quick Google only made things even less clear!!
And(A,B) - true if both A and B are true; for more elements, true if ALL elements are true
Or(A,B) - true if A is true, or B is true, or both are true; for more elements, true if AT LEAST one element is true
Xor(A,B) - Exclusive OR; true if ONLY A is true or ONLY B is true; for more elements, true if
JUST one element is true an odd number of elements are true
True is defined as "1", False is "0". A and B are values or expressions that evaluate to some value. Bool expressions in MC (such as if()/isEqual()/ListContains()/etc) always return "0" or "1".
However, there are some inconsistencies in MC implementation of AND and OR (XOR is not implemented AFAIK). The results are NOT exactly the same as if we just used the "equivalent" Math() expressions mentioned in that page - And() and Or() are more flexible than Math().
MC seems to parse the arguments as numbers, and considers TRUE to be any non-zero value (FALSE is just zero). Examples:
0 = FALSE
1 = TRUE
-1 = TRUE (valid number, non-zero)
blank/empty string = FALSE (as the default argument value is then "0")
9.99 = TRUE (valid number 9; decimals are probably ignored)
0.99 = FALSE (decimals are ignored, so this is a zero)
.99 = FALSE (either parsed as zero or as blank, which is also zero)
apple = FALSE (not a number - note that in some languages this would be TRUE as it's a non-zero/non-null value)
apple123 = FALSE (not a number)
123apple = TRUE (it parses the 123 and ignores the rest)
9.99apple = TRUE (valid number 9, non zero)
-7.5apple = TRUE (still a valid number -7, non-zero)
You may want to document the behaviour.