> just a tip, it's always a good idea to reverse the comparion
What makes you think remembering to swap them over is any easier than remembering to use == ?
What happens when both sides are variables - your safety net is gone, and remembering to use == wins.
What happens to the natural readability of the code?
What happens when 'operand swap zealots' start monkeying around with other operators other than == ?
I've personally seen one example of turning c < 'a' into 'a' < c, and in the process breaking the code in a rather hard to find way.
Get a compiler (like gcc) which warns you when you use = where == was probably intended is a much better choice IMO.