2 ms·
oh my god, this is horrific. I suppose you are just trolling. There's no way this can be an accepted practice anywhere.
by enriquto 7y ago
oh my god, this is horrific. I suppose you are just trolling. There's no way this can be an accepted practice anywhere.
- userbinator 7y agoAs someone who has actually worked with a codebase with plenty of such expressions, I suspect it was really an "accepted practice" at some point in time, stemming from a mindless interpretation of the "be explicit" guideline taken too far. The worst part is that sometimes these redundancies grow and combine to create even more confounding expressions, frequently resulting in monsters resembling this: if ( ((((!(var)!= FALSE)) != TRUE)) ) { return FALSE; } else { return TRUE; }