Let\'s say I have the following code:
struct mytype
{
~mytype() { /* do something like call Mix_CloseAudio etc */ }
};
int main()
{
mytype instant;
Exceptions will call destructors, so long as something in the program catches the exception. If the exception exits the main() function without being caught, the standard does not require the runtime to unwind the stack to clean up.
Using a
try{
// code
}catch(...){ //that elipsis should actually appear in your code
//it doesn't mean I omitted code here.
//code
}
in your main()
function will guarantee that every exception is caught, and all destructors are called.
If you call exit
, the destructor will not be called.
From the C++ standard (§3.6.1/4):
Calling the function
void exit(int);
declared in
<cstdlib>
(18.3) terminates the program without leaving the current block and hence without destroying any objects with automatic storage duration (12.4). If exit is called to end a program during the destruction of an object with static storage duration, the program has undefined behavior.
Yes, calling exit() means the destructor will not be called:
Calling the function void exit(int); declared in
<cstdlib>
(18.3) terminates the program without leaving the current block and hence without destroying any objects with automatic storage duration (12.4). If exit is called to end a program during the destruction of an object with static storage duration, the program has undefined behavior.
If an exception is thrown, on the other hand, the destructor will be called. This is the basis of exception safety in C++.