Timeline for Is it ok to use goto in catch?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2012 at 12:40 | history | edited | Greg | CC BY-SA 3.0 |
Added another way of doing it.
|
| Nov 19, 2012 at 12:14 | comment | added | Greg | I think the classic bug it reduces is preventing recursion overflow in an automated retry situation. Using asynchronous calls also frees up other items to render between retries and does not block the UI. I can imagine a situation where a coder does an automated retry every second in a while loop, the code always raises an exception and the user never gets back control of the UI. I agree it could cause problems if following code depended on success. Though, any code depending on the table fill should be placed in the try block. | |
| Nov 19, 2012 at 9:33 | comment | added | ANeves | ("and decrease bugs" would benefit from an example.) I don't like this approach, because if other methods rely on this method's side-effects this approach will bite the programmer's hand. But it's a nice tool to know, yes. | |
| Nov 18, 2012 at 11:23 | history | edited | Greg | CC BY-SA 3.0 |
added 3 characters in body
|
| Nov 18, 2012 at 11:22 | comment | added | Greg | Asynchronous callbacks are considered very simple to experienced programmers. Novices should learn this pattern. It should be a standard part of a programmers tool box to increase code readability and decrease bugs. | |
| Nov 17, 2012 at 15:18 | comment | added | Leonid | This approach increases the level of complexity (volume of skull sweat required to reason about code that contains such a call) for such a simple problem. | |
| Nov 17, 2012 at 13:01 | history | edited | Greg | CC BY-SA 3.0 |
added 89 characters in body
|
| Nov 17, 2012 at 12:55 | history | answered | Greg | CC BY-SA 3.0 |