GC has a "barbaric" destroyng model, I think

ketmar via Digitalmars-d-learn digitalmars-d-learn at puremagic.com
Thu Feb 12 01:40:11 PST 2015


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.

and it can't be managed by GC too. that's why it has it's own crappy 
pseudo-gc implementation with refcounting. *and* it's memory managemet 
too, heh.
-------------- 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/166f1e7b/attachment.sig>


More information about the Digitalmars-d-learn mailing list