All I know is that I prefer specifying the check with a condition when I am using AND for multi conditional if statements.
I do it when using AND regardless of boolean values. (I still do = 1 or = 0 before using AND for the next condition)
I have had code in the past act flakey until I put that in there, then I got consistent results.
Like I said, I know that is supposed to be okay, it's just my preference to have it when using AND. (not a rule, just my thoughts on it)
AND works in the same way with True & False, so (127 AND 255) will give the result of 1. "
True, the result of an AND is true or false, but the condition the AND is being used for is not always a boolean.
I am not talking about the value being returned by the AND.
I am talking about clarification on condition separation.
Coding things my way since 1981 -- Currently using AppGameKit V2 Tier 1