Obscure C code (was Re: Excessive optimization)

[Philip Pemberton]

On Fri, 2010-12-03 at 17:27 -0800, Eric Smith wrote:
> You've lost me on how that's better than "TF"[!b], or why it would be 
> "more likely to work across different compilers".  There's no tricky 
> pointer math to it.

OK, tricky pointer math wasn't the right way to put it... What I meant
was, it doesn't rely on the compiler returning '0' for a false Boolean
evaluation, and '1' for a True evaluation.

-- 
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/