Currently I set variables False=0 and True=-1 at the start of most programs.
At one point I tried False=0 and True=NOT False - took me a while to debug that error...
Any chance of having embedded constants for TRUE and FALSE?
Something to consider is what would be the value for true and false, which is only a useful adopted convention which can vary.
I use 'flag' variables at the top of the script which can be set =0 to disable something, or =1 to enable it (and sometimes set to higher numbers to change behaviour etc)... so like Bugs, in that context 0=off or false, and 1=true or active.
Things like EspNow functions that return a value; where 0=ok, but non-zero indicates that an error has occurred... so in that context 0=true, and 1 (or any non-zero) denotes false.
If there's logical argument for true=0 false=1 and for false=0 true=1, then as in politics, there's no universally accepted value of true and false.
A debate that could go on forever. Many other languages actually use -1 for false.
As dompie points out, using bitwise logic is another ball-game when the value becomes important if it is to be used in boolean logic.
Personally, I'm not greatly fussed, but I think it requires a bit of thought if they are to be made constants.
