Timeline for Arguments for or against using Try/Catch as logical operators
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2020 at 9:03 | history | edited | Hamedz | CC BY-SA 4.0 |
added 2 characters in body
|
| Sep 13, 2011 at 17:46 | comment | added | back2dos | @jsternbarg: Yes, if/else are in factcompiled to jumps at machine level, but at language level, the jump target is the next statement, while in the case of loops, it's the current statement. I would argue, that that's more of a step, than a jump ;) | |
| Sep 13, 2011 at 17:04 | comment | added | jsternberg | Just putting it out there, if/else is also considered a jump. The difference is that it's a jump that can only occur at that specific spot (and it reads a lot easier) and you don't have to worry about the names of the labels (which you don't have to with try/catch either, but comparing to goto). But just saying "it's a jump, which is bad" also says that if/else is bad, when it isn't. | |
| Sep 13, 2011 at 14:52 | history | made wiki | Post Made Community Wiki by Joeri Sebrechts | ||
| Sep 12, 2011 at 18:49 | history | answered | back2dos | CC BY-SA 3.0 |