I have now undone the corrections I made to nor and nand, and I have removed support for using them with single arguments. The reason I wanted to do this was because "x nand y" would not always return the same truth value as "nand x y", and "x nor y" would not always return the same truth value as "nor x y". I also used grep to check the settings files and include files for single argument uses of nand or nor, and I didn't find any. So I went ahead with the change and made updates to the documentation. This helps remove the possibility that someone could use them to write confusing, obfuscated code. No such issue exists with and and or, as "x and y" will always return the same truth value as "and x y", and "x or y" will always return the same truth value as "or x y".
I did make corrections to and and or similar to the changes described below, but I used ?: instead of if-statements. This did correct how or behaved for or (false), though it didn't change the results I got with and.
I have now undone the corrections I made to nor and nand, and I have removed support for using them with single arguments. The reason I wanted to do this was because "x nand y" would not always return the same truth value as "nand x y", and "x nor y" would not always return the same truth value as "nor x y". I also used grep to check the settings files and include files for single argument uses of nand or nor, and I didn't find any. So I went ahead with the change and made updates to the documentation. This helps remove the possibility that someone could use them to write confusing, obfuscated code. No such issue exists with and and or, as "x and y" will always return the same truth value as "and x y", and "x or y" will always return the same truth value as "or x y".
I did make corrections to and and or similar to the changes described below, but I used ?: instead of if-statements. This did correct how or behaved for or (false), though it didn't change the results I got with and.