Timeline for Single exit of function uses goto
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:45 | history | edited | CommunityBot | replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Nov 14, 2016 at 22:47 | answer | added | dj bazzie wazzie | timeline score: 0 | |
| Oct 28, 2016 at 10:27 | comment | added | CodesInChaos | goto cleanup is fine in C because it lacks other cleanup mechanisms (try...finally, RAII, etc.). | |
| Oct 28, 2016 at 8:17 | answer | added | Pieter B | timeline score: 2 | |
| Oct 28, 2016 at 6:03 | review | Close votes | |||
| Nov 14, 2016 at 3:03 | |||||
| Oct 28, 2016 at 5:36 | comment | added | gnat | Possible duplicate of Where did the notion of "one return only" come from? | |
| Oct 28, 2016 at 5:16 | comment | added | user3824211 | Yes,rwong, it does answer most of the questions, and I am happy to use a goto the return statement to exit early. Then the question of entering a function at different points comes up, and protothreads does serve a very useful purpose, entering a function at different points, and exiting at different points. I don't see anybody arguing against it, so I accept that that is also not wrong. Thank you | |
| Oct 28, 2016 at 4:18 | comment | added | rwong | Doesn't the highest voted answer's approaches answer your question? Also remember that it is legitimate to extract chunks of code into functions, even if those functions would have only one caller, because making the control flow more obvious and verifiable is a legitimate concern on its own. | |
| Oct 28, 2016 at 3:51 | review | First posts | |||
| Oct 31, 2016 at 12:43 | |||||
| Oct 28, 2016 at 3:46 | history | asked | user3824211 | CC BY-SA 3.0 |