“No-else-after-return” considered harmful

Re:“No-else-after-return” considered harmful by makecheck on Sunday August 30, 2009 @11:23PM (#795353)

Functions that have become too complicated should look ugly, so that they're likely to be split into simpler parts (for true readability).

When making that split, it is also helpful to have relevant cleanup code nearby: odds are everything is already in the inner block, instead of having to remove extra code at the end of the function.

[ Parent | on HN ]

Re:“No-else-after-return” considered harmful by antonovka on Monday August 31, 2009 @12:45PM (#796248)

That's the usual hand-waving argument (if you need this you're doing it wrong), but the fact is that even something with three simple preconditions is quickly rendered unreadable through three nested levels of if statements.

[ Parent | on HN ]