News for hackers. Stuff that matters.

A comment on Avoid Else, Return Early (2013). Parent comment

Re:Avoid Else, Return Early (2013) by maxxxxx on Monday March 26, 2018 @10:19AM (#16679063)
I am on board with returning at the beginning while checking arguments. But I hate it when code returns somewhere in the middle for some reason. I have spent countless hours debugging a problem with unexpected behavior only to find a return statement in the middle of a huge block to code.
[ Parent | on HN ]
Re:Avoid Else, Return Early (2013) by augustk on Monday March 26, 2018 @12:19PM (#16679999)
That's because the return statement is a kind of goto statement. Goto-like statements reduce the value of structured programming. In a pure structured program, each statement sequence is either completely executed or not executed. There are also pure structured languages, like Oberon, which doesn't allow impurely structured programs.
[ Parent | on HN ]
Re:Avoid Else, Return Early (2013) by maxxxxx on Monday March 26, 2018 @01:20PM (#16680613)
When return is used in the middle of a complex code sequence I much prefer a goto so at least I know where all paths exit.
[ Parent | on HN ]