Access Violation Tracking

[ketmar via Digitalmars-d-learn]

On Sun, 09 Nov 2014 09:33:29 -0500
Etienne via Digitalmars-d-learn <digitalmars-d-learn at puremagic.com>
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. ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-learn/attachments/20141109/95345601/attachment.sig>