Am 13.10.2012 21:15, schrieb Tim E. Real: > On October 12, 2012 05:02:52 PM Florian Jung wrote: >> Am 30.09.2012 19:55, schrieb WillyFoobar: >>> Hello together, >>> >>> this weekend I had the time to download and check the >>> muse-2.0.1.tar.gz for compile time warnings. >> >> Hi, >> >> thanks, i've committed the changes to trunk. >> >> please mail us a patch (generated by "svn diff" in the trunk directory >> (or whatever branch you were on)) the next time, this is much easier to >> apply. >> >> i wasn't able to locate the places in midi.cpp where you had changes; >> what did you mean there? >> >> greetings >> flo > > Thanks Willy! > And thanks Flo. > > I too have fixed a few places before, for > virtual destructors. > > Virtual destructors seem to be a sort of > grey area, often having their own chapter > in books. They seem like the defacto thing > to do yet for some reason they seem > misunderstood and seem to have reasons why > they need to be treated different from > other virtual methods. > > In other words there's more to the story > with virtual destructors than there is > with other virtual methods. > Something about the calling sequence > if I recall...
really? tell me more. sources? AFAIK, virtual destructors must be used when a) a Base* which points to a Derived gets deleted b) Derived can somehow bind ressources (malloc, new, open etc) Base does not know of, i.e. Base cannot free. i haven't heard of any nasty calling order problems with virtual or non-virtual dtors. (because first ~Derived, then ~Base is called, so the vtable is still intact, right?) (the only problem i'm aware of is that the Base-ctor may not call any virtual functions from Derived, because at the point where Base is called, the Derived-parts of the memory (including the vtable places) are yet undefined) greetings flo
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
