Well, starting from “Or” considered harmful. we noticed that the distinction of andor, xor and ewok is certainly a useful concept, however, the naming scheme leaves room for improvement. Andor is certainly too long for practical usage and ewok always raises associations to small furry creatures.
On the quest for appropriate names we thought that or certainly suffices for andor, just like (mathematical) logic tells us. Xor is short and pronounceable enough for everyday use and the meaning is clear with the usual knowledge of geeks. This leaves ewok. sh suggested eor, which may be interpreted as ewok-or. It does not sound too stupid, is short enough and thus quite usable.
The only challenge now is to switch my writing and talking habits over to those new words :-)
d.IsNullity() instead of d.IsNaN().
Just my two cents on this issue.
Wikinews has a little more opinions on this. A while ago I tried writing a postscript function that draws flux lines for electric current or magnetic fields. While this still hasn't happened I wrote essentially all vector operations in 2D I could think of and those are collected in the attached file. Nothing too fance but as optimized as I could. All functions are bound, thus will be precompiled and use only stack operations, no dictionaries.