7 ms·
Typically that isn't done from ignorance, just some (imho misguided) idea about readability.
by jlgreco 13y ago
Typically that isn't done from ignorance, just some (imho misguided) idea about readability.
- arethuza 13y agoProbably the same kind of place that bans use of the ternary conditional operator because it's "too complicated" <sigh>
- jlgreco 13y agoEh, I can't say that I have any love for the ternary if operator. It is an ugly construct made necessary by the other flow control constructs being statements. Scala lets you just use if/else like that, the result is much clearer at the cost of 4 or so characters.
- sigkill 13y agoGuilty as charged. Although it's practically the same, I prefer the TRUE part. Same with the !aBoolean and FALSE.
- chanux 13y agoI saw this in some coding standard for PHP.
- andyroid 13y agoWhere it actually makes sense (assuming === and not == is used for comparison).