> If the 'op' is a compile-time constant and the "function" is either inline
> or a macro, you get the same effect without having to expand the name space
> of the API for each new 'op' you may add.

Is the name space of the API that precious a commodity?

I'm not sure that preserving it is worth the cost of having a complex
macro with an unreadable nest of ?: operators, or an overly large
inline function which *definitely* bloats up the code if someone makes
the mistake of passing a variable op to it.

					- Bill