From: shiwei xu (xushiweizh_at_[hidden])
Date: 2008-04-22 20:55:47
I agree you. But you know "GC Allocator" is OPTIONAL, not a MUST. I don't
think it is all of C++ memory management.
On Wed, Apr 23, 2008 at 2:44 AM, Steven Watanabe <watanabesj_at_[hidden]>
> If I understand correctly, your GC allocators delete all
> allocated blocks when the allocator itself is destroyed,
> or can be explicitly forced to free everything. Basically,
> this works by imposing a hard upper bound on the lifetime
> of a group of objects, rather than dealing with them separately.
> I think that this is useful in some contexts. (Enough that I implemented
> a simple version about a year ago). However, it is not
> always applicable. Consider your List template. As I understand
> it, if I have a List that exists for the duration of the program,
> and I am often adding and removing elements, then the
> memory for the elements will just build up until the List
> is destroyed.
> In Christ,
> Steven Watanabe
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk