I’m not super familiar with BASIC. Can you explain how the definition of One works? If variables have random values when declared but not set due to memory garbage, I would expect ZeroBit to be “true” half the time and “false” the other half. When it’s false, I can reason through it, but when it’s true I don’t see it. I imagine it has something to do with the details of ABS()?
Indeed. But…
If One was defined as random garbage, then still…
Zero=One-One
See my definition of One afterwards, it’s a bit awkward, but works…
Edit: Stop using digits, 0 is a digit…
I’m not super familiar with BASIC. Can you explain how the definition of One works? If variables have random values when declared but not set due to memory garbage, I would expect ZeroBit to be “true” half the time and “false” the other half. When it’s false, I can reason through it, but when it’s true I don’t see it. I imagine it has something to do with the details of ABS()?
Different BASIC dialects work differently, you’re absolutely right to ask.
Honestly, the ZeroBit code part is the hack within Mobile Basic, it always returns Zero, meaning the ABS(NOT(ZeroBit)) will always return One