You jest, but on some older computers, all ones was the official truth value. Other values may also have been true in certain contexts, but that was the guaranteed one.
I was programming in assembly for ARM (some cortex chip) and I kid you not the C program we were integrating with required 255, with just 1 it read it as false
I set all 8 bits to 1 because I want it to be really true.
You jest, but on some older computers, all ones was the official truth value. Other values may also have been true in certain contexts, but that was the guaranteed one.
TIL, 255 is the new 1.
Aka -1 >> 1 : TRUE
But only if you really mean it. If not, it’s a syntax error and the compiler will know.
01111111 = true
11111111 = negative true = false
So all this time true was actually false and false was actually true ?
Depends on if you are on a big endian or little endian architecture.
Come on man, I’m not gonna talk about my endian publicly
negative true = negative non-zero = non-zero = true.
What if it’s an unsigned boolean?
Super true.
Cthulhu shows up.
Common misconception… Unsigned booleans (ubool) are always 16-bits.
00001111 = maybe
10101010 = I don’t know
00000001 00000000 00001111 10101010
100001111 = maybe not
0011 1111 = could you repeat the question
Schrödingers Boolean
Is this quantum computing? 😜
Could also store our bools as floats.
00111111100000000000000000000000is true and10111111100000000000000000000000is negative true.Has the fun twist that true & false is true and true | false is false .
Why do alternative facts always gotta show up uninvited to the party? 🥳
I was programming in assembly for ARM (some cortex chip) and I kid you not the C program we were integrating with required 255, with just 1 it read it as false