T
Timothy Madden
Hello
I have just read (in a MSDN article named Deep C++, in part 8) that
member functions operator new and operator delete (and operator new[]
and operator delete[]) are required in order to have the language
automaticaly delete a memory bloc alocated with _new_ after the
constructor for the new object throws.
Is it true that only class delete is called in a new expresion to free
memory after the constructor throw ?
I am trying to write an exception-safe application. Idealy the app will
never crash, but will pop-up a message box and exit gracefully with full
clean-up if a fatal error like access violation occurs, be it anywhere
in the flow of control in my app. However I find this to be such a
difficult task to do !! It is ever more complicated.
Do you know of a good book that will fully explain to me how to
effectively use exception-handling in a real application ? The problem
gets even worse if you work with the odd code and design required by
Win32 and Win32 GUI...
Thank you
Timothy Madden
Romania
I have just read (in a MSDN article named Deep C++, in part 8) that
member functions operator new and operator delete (and operator new[]
and operator delete[]) are required in order to have the language
automaticaly delete a memory bloc alocated with _new_ after the
constructor for the new object throws.
Is it true that only class delete is called in a new expresion to free
memory after the constructor throw ?
I am trying to write an exception-safe application. Idealy the app will
never crash, but will pop-up a message box and exit gracefully with full
clean-up if a fatal error like access violation occurs, be it anywhere
in the flow of control in my app. However I find this to be such a
difficult task to do !! It is ever more complicated.
Do you know of a good book that will fully explain to me how to
effectively use exception-handling in a real application ? The problem
gets even worse if you work with the odd code and design required by
Win32 and Win32 GUI...
Thank you
Timothy Madden
Romania