query: try/finally without catch and return value
positive_passages.docid: 2277
positive_passages.text: Does a finally block always get executed in Java?
negative_passages.docid: 22386
negative_passages.text: 'using' statement vs 'try finally'
negative_passages.docid: 126364
negative_passages.text: Java try-finally return design question
negative_passages.docid: 28606
negative_passages.text: Is it a good approach to call return inside using {} statement?
negative_passages.docid: 126986
negative_passages.text: Multiple returns: Which one sets the final return value?
negative_passages.docid: 151585
negative_passages.text: Can I force a function to quit and return some value after a certain amount of time has passed during its evaluation?
negative_passages.docid: 55592
negative_passages.text: What is the proper way to re-throw an exception in C#?
negative_passages.docid: 85501
negative_passages.text: Why use finally in C#?
negative_passages.docid: 80292
negative_passages.text: Handling unhandled exceptions problem
negative_passages.docid: 134996
negative_passages.text: How can I temporarily disable the "return value might be undefined" warning?
negative_passages.docid: 70983
negative_passages.text: How can I use '*' to capture everything with exceptions
negative_passages.docid: 79805
negative_passages.text: Which is better, return value or out parameter?
negative_passages.docid: 23488
negative_passages.text: "Missing return statement" within if / for / while
negative_passages.docid: 35193
negative_passages.text: Is it better to use an exception or a return code in Python?
negative_passages.docid: 41562
negative_passages.text: Embed the existing code of a method in a try-finally block (2)
negative_passages.docid: 78574
negative_passages.text: Java io ugly try-finally block
negative_passages.docid: 53171
negative_passages.text: return eats exception