|Problems? Is your data what you think it is?|
But I've come to find ternaries to often be less quick/easy to read than something like:
I am with BrowserUK here, and I am happy to see you are using the "I find" instead of the way to often used "it is better to" (here in the monastery), as many idioms that are easy to parse by person A causes headaches to person B.
Personally I would try to avoid statement modifiers to any cost. I hate them. They make me read code exactly opposite of what the author meant.
I have no trouble reading (nested) ternary operations. Maybe too used to those from doing C.
You also doing java? Where 42 == $n is quite often preferred over $n == 42 because of "string".equals ($n) implies NULL checks.
Enjoy, Have FUN! H.Merijn
In reply to Re^2: Two simple code style advice questions (tye)