very cool Billy.  I agree, much cleaner, more maintainable, and more readable.  Great post!

Good one Billy...I'll keep an eye out where I can use this to clean things up a bit...

Pretty cool as always. Though I must say that I think that most guys will always prefer the 1st aproach (I prefer the 2nd too, but my experience shows that people will write the second option even though they know about xor...)

I find that most programmers don't have a clue about even basic boolean algebra!  Even the basics like Demorgan's theorem

to whit

if you have

!A and !B

it is the sane as

!(A or B)

and

!A or !B is

!(A and B)

where this comes in useful is for things like

!(!A or B)

which becomes

!!A and !B

or

A and !B

"break the bar, reverse the and/or" (in logic class a bar over the variable is the "not")

Pingback from  » Daily Dose of Links - 20071205 Alvin Ashcraft’s Daily Geek Bits: Daily links plus random ramblings about development, gadgets and raising rugrats.

The way I always remember XOR is by saying it's "your  momma's OR":

"You can have cake OR pie for dessert ... but not both."

well how to do a XOR if there are 3 conditions, say for instance i want a true only if one of a,b,c is = 10

i.e. ((a==10) ^ (b==10) ^ (c==10)) it does not work this way in code i have checked (i use C#)