That is like C++ destructors, which are called deterministically when they go out of scope (again with no "try" syntax). They can unlock mutexes, close files, etc. But unlike what you describe, there is no need to put anything at the end of the function: instead, the fact that you have instantiated an object already guarantees that its destructor will be called later. This is called RAII, short for "resource acquisition is initialisation".

Yes... RAII is handy, but it doesn’t save you from checking EOF logic in my example.

You could use a File class that throws on EOF, but that would be a really bad idea for C++ since throw/catch are very expensive.

Exceptions are expensive compared to a simple function call, but I imagine they're cheap compared to operations that read from disk. Certainly one exception per file close is not going to hurt.

> don’t include logic for checking for EOF. Let the exception handler catch it where the file will be closed

What happens if the file is smaller than you anticipate?

That's why exceptions aren't used for flow control.

Simply count bytes as they are read. In the exception handler check to see if the count matches the expected value. Clean.