The two code blocks you gave are not equivalent The code you described as old way of doing things has a serious bug: in case opening the file fails you will get a second exception in the finally clause because f is not bound. The equivalent old style code would be: try: f = open(“file”, … Read more
from the Sun Tutorials Note: If the JVM exits while the try or catch code is being executed, then the finally block may not execute. Likewise, if the thread executing the try or catch code is interrupted or killed, the finally block may not execute even though the application as a whole continues. I don’t … Read more
If any of the code in the try block can throw a checked exception, it has to appear in the throws clause of the method signature. If an unchecked exception is thrown, it’s bubbled out of the method. The finally block is always executed, whether an exception is thrown or not.
“Guaranteed” is a much stronger word than any implementation of finally deserves. What is guaranteed is that if execution flows out of the whole try–finally construct, it will pass through the finally to do so. What is not guaranteed is that execution will flow out of the try–finally. A finally in a generator or async … Read more
No, C++ does not support ‘finally’ blocks. The reason is that C++ instead supports RAII: “Resource Acquisition Is Initialization” — a poor name† for a really useful concept. The idea is that an object’s destructor is responsible for freeing resources. When the object has automatic storage duration, the object’s destructor will be called when the … Read more