try-catch-finally

问题 We have a scan that aborts on the code below, with the exception: org.sonar.java.se.ExplodedGraphWalker$MaximumStepsReachedException: reached limit of 16000 steps for method getServiceProviders#151 in class ServiceProviderService We looked at rules S2259 and S2583 and would like to keep notifications about null pointers. This happens in both "regular" and debug (-X) mode, so it's not issue 1406. In our case it really seems to be related to try/catch. (See sample method below.) Could it be a

问题 We have a scan that aborts on the code below, with the exception: org.sonar.java.se.ExplodedGraphWalker$MaximumStepsReachedException: reached limit of 16000 steps for method getServiceProviders#151 in class ServiceProviderService We looked at rules S2259 and S2583 and would like to keep notifications about null pointers. This happens in both "regular" and debug (-X) mode, so it's not issue 1406. In our case it really seems to be related to try/catch. (See sample method below.) Could it be a

问题 I need a way to break from the middle of try/catch block without throwing an exception. Something that is similar to the break and continue in for loops. Is this possible? I have been getting weird throughts about throwing a custom exception (naming it "BreakContinueException") that simple does nothing in its catch handler. I'm sure this is very twisted. So, any straight forward solution I'm not aware of? 回答1: The proper way to do it is probably to break down the method by putting the try

问题 Is there a reason why the following wouldn't work? @try { CFGetTypeID( NULL ); } @catch (NSException * e) { NSLog(@"Exception: %@", e); } @finally { NSLog(@"finally"); } Similar to the try/catch question, only it seems the above block crashes everytime. I know my debugger is setup correctly, as I setup a try/catch above from the other question: // Test working try catch NSString* test = [NSString stringWithString:@"ss"]; @try { [test characterAtIndex:6]; } @catch (NSException * e) { NSLog(@

问题 try { FileReader fr = new FileReader(file); BufferedReader br = new BufferedReader(fr); String line = null; } catch (FileNotFoundException fnf) { fnf.printStackTrace(); } finally { fr.close(); } The fr.close() shows an error: fr cannot be resolved I had read that closing a file in the finally block is a good practice. What is that am doing wrong? 回答1: The variable fr only has scope within the try block. It is out of scope in the finally block. You need to declare it before the try block:

问题 I see that the Finally in Try .. Catch will always execute after any parts of the execution of the try catch block. Is it any different to just skip the Finally section and just run it after, outside the try catch block? Example 1, Try ... Catch ... Finally ... End Try Try 'Do something Catch ex As Exception 'Handle exception Finally 'Do cleanup End Try Example 2, Try ... Catch ... End Try ... Do the finally stuff outside Try 'Do something Catch ex As Exception 'Handle exception End Try 'Do

问题 In SQL Server, is there something similar to finally clause in try..catch... block of c# ? I mean, I am using BEGIN TRAN, END TRAN, COMMIT TRAN, ROLLBACK TRAN etc in a SQL Server transaction and want a section or some set of actions that needs to fire irrespective of success or failure or transaction. Is there a solution for that? (similar to finally block on try/catch of OOPS languages). Thanks in advance 回答1: There isn't anything that will run "irrespective of success or failure" with 100%

问题 Consider these two examples <?php function throw_exception() { // Arbitrary code here throw new Exception('Hello, Joe!'); } function some_code() { // Arbitrary code here } try { throw_exception(); } catch (Exception $e) { echo $e->getMessage(); } some_code(); // More arbitrary code ?> and <?php function throw_exception() { // Arbitrary code here throw new Exception('Hello, Joe!'); } function some_code() { // Arbitrary code here } try { throw_exception(); } catch (Exception $e) { echo $e-

问题 For any possible try-finally block in Python, is it guaranteed that the finally block will always be executed? For example, let’s say I return while in an except block: try: 1/0 except ZeroDivisionError: return finally: print("Does this code run?") Or maybe I re-raise an Exception : try: 1/0 except ZeroDivisionError: raise finally: print("What about this code?") Testing shows that finally does get executed for the above examples, but I imagine there are other scenarios I haven't thought of.

问题 This question already has answers here : Does a finally block always get executed in Java? (47 answers) Closed 6 years ago . Given the following try/catch block in java: try{ return; } catch(SomeException e){ System.out.println(e); } finally{ System.out.println("This is the finally block"); } and according to this post: "Does finally always execute in Java?" I can see that the program's output will be 'This is the finally block'. However, I can't figure out how that would be possible since