Am Donnerstag, 20. Juni 2013 schrieb Jan Kundrát <j...@flaska.net>: > Now I'm confused -- your mail suggests to omit the destructor altogether, and at the same time you quote a document saying that one should always include it. I agree with the quoted document :).
The important part here is that there /is/ a virtual deconstructor in the base class (where it /has/ to be if you don't want funny effects on deconstruction) It's not going away and every inheritance implemented deconstructor will be virtual as well - also the autogenerated. It's not required to explicitly add it there for nothing to do. If you're however going to add one, it shall not be inline. Actually rather no non-private function in a library interface should be inline. I'm not aware of a relevant linker where the absence of such explicit inherited virtual deconstructor would get you type issues (but i'm oc. not aware of everything =) Cheers, Thomas
