RE: object_pool, O(N) destroy?

From: scleary_at_[hidden]
Date: 2002-01-29 00:12:55

> -----Original Message-----
> From: hicks [mailto:hicks_at_[hidden]]
> 
> It sounds like a case where a type trait, identifying the need for the 
> pool to responsible for deletion,
> would be appropriate.  Then objects which did not need to be destroyed 
> (e.g. ptrs, "plain" structs)
> could be handled by optimized code.  But that's more work than cut and 
> paste.

Actually, the difference is in how the pool is used, not on the type of
object being allocated.  So it sounds more like a case for a policy-based
design.  Too bad, I just don't have time to do that right now... :(

        -Steve