A method should only catch an exception when it can handle it in some sensible way. Otherwise, pass it on up, in the hope that a method higher up the call stack can make sense of it. As others have noted, it is good practice to have an unhandled exception handler (with logging) at the … Read more
This has been possible since Java 7. The syntax for a multi-catch block is: try { … } catch (IllegalArgumentException | SecurityException | IllegalAccessException | NoSuchFieldException e) { someCode(); } Remember, though, that if all the exceptions belong to the same class hierarchy, you can simply catch that base exception type. Also note that you … Read more
traceback.format_exc() or sys.exc_info() will yield more info if that’s what you want. import traceback import sys try: do_stuff() except Exception: print(traceback.format_exc()) # or print(sys.exc_info()[2])
Check it. static public void Main(string[] args) { Stopwatch w = new Stopwatch(); double d = 0; w.Start(); for (int i = 0; i < 10000000; i++) { try { d = Math.Sin(1); } catch (Exception ex) { Console.WriteLine(ex.ToString()); } } w.Stop(); Console.WriteLine(w.Elapsed); w.Reset(); w.Start(); for (int i = 0; i < 10000000; i++) { … Read more
You should prefer try/except over if/else if that results in speed-ups (for example by preventing extra lookups) cleaner code (fewer lines/easier to read) Often, these go hand-in-hand. speed-ups In the case of trying to find an element in a long list by: try: x = my_list[index] except IndexError: x = ‘NO_ABC’ the try, except is … Read more
My exception-handling strategy is: To catch all unhandled exceptions by hooking to the Application.ThreadException event, then decide: For a UI application: to pop it to the user with an apology message (WinForms) For a Service or a Console application: log it to a file (service or console) Then I always enclose every piece of code … Read more
First; the way that the code in the article does it is evil. throw ex will reset the call stack in the exception to the point where this throw statement is; losing the information about where the exception actually was created. Second, if you just catch and re-throw like that, I see no added value, … Read more
Maybe this is the same as your solution, but I wrote a factory to convert plain old functions into functions that capture their values, errors, and warnings, so I can test <- function(i) switch(i, “1”=stop(“oops”), “2”={ warning(“hmm”); i }, i) res <- lapply(1:3, factory(test)) with each element of the result containing the value, error, and … Read more
“I do not know if it is out of ignorance, but I do not like that kind of programming, as it is using exceptions to perform flow control.” In the Python world, using exceptions for flow control is common and normal. Even the Python core developers use exceptions for flow-control and that style is heavily … Read more
Usually empty try-catch is a bad idea because you are silently swallowing an error condition and then continuing execution. Occasionally this may be the right thing to do, but often it’s a sign that a developer saw an exception, didn’t know what to do about it, and so used an empty catch to silence the … Read more