Catch exceptions in main()? about bloaty HOT 7 CLOSED

We do not use exceptions per the Google style guide: https://google.github.io/styleguide/cppguide.html#Exceptions

Some of the standard library functions can throw exceptions if you call them incorrectly. But I see this as being like assertion failures: they can and should cause the program to abort. I don't see any benefit to catching exceptions in main().

from bloaty.

Which behaviour do you expect from the software implementation if a C++ exception will not be caught/handled there?

from bloaty.

All I care is that the exception is printed to the screen and the program exits. I don't care if destructors are called.

from bloaty.

I would care more if the desired destructors are called also before program termination.

from bloaty.

Why does that matter? The OS will clean up any resources we were holding. I can't see any reason that it helps us to ensure destructors are called.

from bloaty.

Can destructors contain special functionality where it is important to execute the corresponding code also at the end?

from bloaty.

Bloaty has some destructors that perform cleanup. For example this destructor will call munmap(): https://github.com/google/bloaty/blob/master/src/bloaty.cc#L1185

But all of these cleanup functions will be performed automatically by the OS when the program exits. There is really no benefit to manually cleaning up resources that the OS will clean up for you anyway.

from bloaty.