404'd! :D

yuck, I would shoot anyone on my team who nested 5+ ternary operators. If you want to get rid of the IF ELSE lists replace it with another construct, not a shortcut to the exact same construct.

read the comments...went over like walking into a classic cafe and asking where Starbucks is. :-)

I am terrified now. I have seen bad code, but......

You people are hilarious.

What a fuss over a stupid article about a simple language feature that few people know about. The code sample I gave is not complicated, and cleaner than the if-then-else way of writing it, *IN THIS SPECIFIC CASE*. And in this case, even if someone doesn't have a clue about what the ternary operator does, he/she will still capture the meaning of that piece of code, because of the way it is written.

I would never recommend this pattern for performing complex conditional assignments. It's just a piece of code showing the "special" behavior of a right-associative operator such as the ternary operator.