Eliminate class allocators and deallocators?

dsimcha dsimcha at yahoo.com
Wed Oct 7 11:17:31 PDT 2009


== Quote from Andrei Alexandrescu (SeeWebsiteForEmail at erdani.org)'s article
> It is a bad idea because distinguishing between release of (expensive)
> resources from dangerous memory recycling is the correct way to obtain
> deterministic resource management within the confines of safety.

This is based on two faulty assumptions:

1.  Memory is cheap.  (Not if you are working with absurd amounts of data).
2.  Garbage collection is never a major bottleneck.  (Sometimes it's a worthwhile
tradeoff to add a few manual delete statements to code and sacrifice some safety
for making the GC run less often.)



More information about the Digitalmars-d mailing list