Why Is It Not A Good Idea To Use Empty Destructors?

1.	Why Is It Not A Good Idea To Use Empty Destructors?
Answer» When a CLASS contains a DESTRUCTOR, an entry is created in the FINALIZE queue. When the destructor is called, the garbage collector is INVOKED to process the queue. If the destructor is empty, this just causes a needless loss of performance. When a class contains a destructor, an entry is created in the Finalize queue. When the destructor is called, the garbage collector is invoked to process the queue. If the destructor is empty, this just causes a needless loss of performance.

Answer»

When a CLASS contains a DESTRUCTOR, an entry is created in the FINALIZE queue. When the destructor is called, the garbage collector is INVOKED to process the queue. If the destructor is empty, this just causes a needless loss of performance.

When a class contains a destructor, an entry is created in the Finalize queue. When the destructor is called, the garbage collector is invoked to process the queue. If the destructor is empty, this just causes a needless loss of performance.

Discussion

No Comment Found

Related InterviewSolutions

What's The Difference Between <c> And <code> Xml Documentation Tag?
What's A Satellite Assembly?
What's A Multicast Delegate?
What's The C# Equivalent Of C++ Catch (...), Which Was A Catch-all Statement For Any Possible Exception?
What's Class Sortedlist Underneath?
What Is The Difference Between Proc. Sent By Val And By Sub?
Which Control Cannot Be Placed In Mdi?
Which Property Of The Textbox Cannot Be Changed At Runtime?
What Is The Maximum Size Of The Textbox?
Which Controls Do Not Have Events?

Why Is It Not A Good Idea To Use Empty Destructors?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment