Timeline for Where did the notion of "one return only" come from?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2021 at 9:41 | comment | added | Toby Speight | A good debugger should allow you to breakpoint all returns at once. If your debugger doesn't, consider contributing to improve it (unless it's closed-source, in which case you should probably switch). | |
| Jun 11, 2020 at 13:56 | comment | added | gnasher729 | Up to everyone to decide themselves. Nevertheless, your first comment was nonsense. | |
| Jun 11, 2020 at 13:53 | comment | added | Robert Harvey | It's not a good enough reason to upend your entire coding style. Early exit is a very useful technique; it cleans up endless if-else ladders, and greatly simplifies the logic. | |
| Jun 11, 2020 at 13:48 | comment | added | gnasher729 | Robert, I would have expected better from you. f(self.prop1, self.prop2, self.prop3). Now set a breakpoint to get the return value of prop2. | |
| Jun 10, 2020 at 16:51 | comment | added | Robert Harvey | Set a breakpoint at the point of origin, where the function was called, and examine the return value there. | |
| S Jun 10, 2020 at 16:48 | history | answered | gnasher729 | CC BY-SA 4.0 | |
| S Jun 10, 2020 at 16:48 | history | made wiki | Post Made Community Wiki by gnasher729 |