On Sun, 09 Nov 2014 09:33:29 -0500 Etienne via Digitalmars-d-learn <[email protected]> wrote:
> I've seen a lot more invalid memory operation errors since the GC calls > destructors. Letting the GC destroy objects out of order can be the > issue. We might have to make an associative array of static global flags > (debug bool[void*]) for each object to see if it was destroyed, and use > asserts in the destructors / update the associative array, as a new idiom. that's where i want precise GC to come into play. i really want it to nullify all internal pointers to finalized objects before calling destructor. sure, this can modify alot of members, so it must be opt-in feature. ah, and stop calling class finalizers "destructors" helps too. they are... well... finalizers, not destructors. ;-)
signature.asc
Description: PGP signature
