CException
-
Do I have always to call the CException::Delete method to make sure that it is always deleted? Best regards, Alexandru Savescu
-
Do I have always to call the CException::Delete method to make sure that it is always deleted? Best regards, Alexandru Savescu
If you get a reference to an CException object you should call Delete() to prevent memory loss. Vezi ca e important cum construiesti obiectul ala CException( BOOL b_AutoDelete ); ... asa pe romaneste :) Bye, Orbital^ ...the night is long ... but not long enought to do some real coding ...
-
If you get a reference to an CException object you should call Delete() to prevent memory loss. Vezi ca e important cum construiesti obiectul ala CException( BOOL b_AutoDelete ); ... asa pe romaneste :) Bye, Orbital^ ...the night is long ... but not long enought to do some real coding ...
I think we should post in English only. :) I catch a pointer to a CDBException that I didn't create myself, it was thrown by MFC like this:
try
{
// database operations that may throw exceptions
}
catch (CDBException* e)
{
// should I call Delete?
}Best regards, Alexandru Savescu
-
I think we should post in English only. :) I catch a pointer to a CDBException that I didn't create myself, it was thrown by MFC like this:
try
{
// database operations that may throw exceptions
}
catch (CDBException* e)
{
// should I call Delete?
}Best regards, Alexandru Savescu
You have to always delete exception, when you catch it as pointer to it.
-
You have to always delete exception, when you catch it as pointer to it.
Martin Ziacek wrote: You have to always delete exception, when you catch it as pointer to it. I thought so. Thanks! Best regards, Alexandru Savescu