I have a loop that looks something like this: for (int i = 0; i < max; i++) { String myString = …; float myNum = Float.parseFloat(myString); myFloats[i] = myNum; } This is the main content of a method whose sole purpose is to return the array of floats. I want this method to return … Read more
I have seen people say that it is bad form to use catch with no arguments, especially if that catch doesn’t do anything: StreamReader reader=new StreamReader(“myfile.txt”); try { int i = 5 / 0; } catch // No args, so it will catch any exception {} reader.Close(); However, this is considered good form: StreamReader reader=new … Read more
Closed. This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 6 years ago. Improve this question I’ve just seen a question on try-catch, which people (including Jon Skeet) say empty catch blocks … Read more
We know that it is expensive to catch exceptions. But, is it also expensive to use a try-catch block in Java even if an exception is never thrown? I found the Stack Overflow question/answer Why are try blocks expensive?, but it is for .NET. 7 Answers 7
while maintaining my colleague’s code from even someone who claims to be a senior developer, I often see the following code: try { //do something } catch { //Do nothing } or sometimes they write logging information to log files like following try catch block try { //do some work } catch(Exception exception) { WriteException2LogFile(exception); … Read more
Which one: using (var myObject = new MyClass()) { try { // something here… } catch(Exception ex) { // Handle exception } } OR try { using (var myObject = new MyClass()) { // something here… } } catch(Exception ex) { // Handle exception } 9 Answers 9
Try-catch is meant to help in the exception handling. This means somehow that it will help our system to be more robust: try to recover from an unexpected event. We suspect something might happen when executing and instruction (sending a message), so it gets enclosed in the try. If that something nearly unexpected happens, we … Read more
I’m reviewing some code for a friend and say that he was using a return statement inside of a try-finally block. Does the code in the Finally section still fire even though the rest of the try block doesn’t? Example: public bool someMethod() { try { return true; throw new Exception(“test”); // doesn’t seem to … Read more
During a code review with a Microsoft employee we came across a large section of code inside a try{} block. She and an IT representative suggested this can have effects on performance of the code. In fact, they suggested most of the code should be outside of try/catch blocks, and that only important sections should … Read more
I often see comments on other Stack Overflow questions about how the use of except: pass is discouraged. Why is this bad? Sometimes I just don’t care what the errors are and I want to just continue with the code. try: something except: pass Why is using an except: pass block bad? What makes it … Read more
