You need to be as specific as possible. Otherwise unforeseen bugs might creep away this way. Besides, Throwable covers Error as well and that’s usually no point of return. You don’t want to catch/handle that, you want your program to die immediately so that you can fix it properly.
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
Andrew Grant’s answer does not help getting a stack trace of the throwing function, at least not with GCC, because a throw statement does not save the current stack trace on its own, and the catch handler won’t have access to the stack trace at that point any more. The only way – using GCC … Read more
Generally, never. However, sometimes you need to catch specific errors. If you’re writing framework-ish code (loading 3rd party classes), it might be wise to catch LinkageError (no class def found, unsatisfied link, incompatible class change). I’ve also seen some stupid 3rd-party code throwing subclasses of Error, so you’ll have to handle those as well. By … Read more
Here’s the complete solution (almost: I omitted the UI layout and button handling) – derived from a lot of experimentation and various posts from others related to issues that came up along the way. There are a number of things you need to do: Handle uncaughtException in your Application subclass. After catching an exception, start … Read more
You need to check it yourself and throw an exception. Integer divide by zero is not an exception in standard C++. Neither is floating point divide by zero but at least that has specific means for dealing with it. The exceptions listed in the ISO standard are: namespace std { class logic_error; class domain_error; class … 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
What is the difference between the following ways of handling InterruptedException? What is the best way to do it? You’ve probably come to ask this question because you’ve called a method that throws InterruptedException. First of all, you should see throws InterruptedException for what it is: A part of the method signature and a possible … 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
It’s somewhat weird to read but yes, the exception will bubble up to the calling code – but only if you await or Wait() the call to Foo. public async Task Foo() { var x = await DoSomethingAsync(); } public async void DoFoo() { try { await Foo(); } catch (ProtocolException ex) { // The … Read more