XOR and XNOR operations with 2 or 3 inputs

dlloyd:
011 triggers the XOR because the code is testing for inequality which is simpler. For the XNOR, it tests for the equality condition which is simpler in that case.

EDIT: With the previously attached scripts, I used "random(0, 256)" for x, y, and z and even after about 5 minutes on the Arduino Due, there were still no invalid results on the print monitor.

Well, it's simpler, and agrees with the "odd number of inputs" principle as described on the Wiki page posted earlier, so I guess that works. Not at all what I would expect the result to be, but I guess I would have a rude awakening in that regard with real-life hardware as well.

If you're happy, I'm happy.