GC has a "barbaric" destroyng model, I think

[ketmar via Digitalmars-d-learn]

On Thu, 12 Feb 2015 09:26:12 +0000, Kagamin wrote:

> That's a repetition of C++ atavism, that resource management == memory
> management. IStream is a traditional example of a GC-managed object,
> which needs deterministic destruction, and not because it consumes
> memory, but because it encapsulates an unmanaged resource, it has
> nothing to do with memory management, malloc and free.

p.s. istream example is bad. what it does is simply highlighting the fact 
that there is no way to do deterministic management with GC.
-------------- 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/20150212/4fc50ca9/attachment.sig>