
Peter Soetens wrote:
On Mon, Oct 12, 2009 at 20:18, Steven Watanabe
wrote: AMDG
Because there's a better fix that guarantees that it will work correctly on all compilers...
Which I must have missed. What better fix has been confirmed to solve this problem ?
Yes. I've fixed the issue some time ago.
Just #ifdef the virtual around the destructor for GNU compilers and we can all happily carry on.
IMO, it's a bad idea to throw in a hack to fix a problem without understanding why it works.
I'm not sure what you're aiming at (my understanding or yours), but this is not an argument. What we do know is that making the destructor virtual and dropping the cast will produce the correct behavior for virtually every C++ compiler out there.
The virtual destructor produces virtually correct behavior on virtually every C++ compiler virtually every time ;) Gennadiy