Subject: Re: [boost] copy on write for std containers
From: Peter Foelsche (foelsche_at_[hidden])
Date: 2010-12-04 19:33:26
"Jeffrey Lee Hellrung, Jr." <jhellrung_at_[hidden]> wrote in message
> I think the point is that copy-on-write is rarely optimal, often
> suboptimal, and increases complexity; hence it should not be encouraged.
increases complexity -- wrong -- I only replaced the matching types -- the
using code was not modified.
The number of lines for the wrapper are minimal -- I only implemented the
methods I'm using.
I don't care about complexity the compiler has to manage.
I care about the complexity I have to manage.
I could introduce some filtering to avoid storing identical instances which
would even more decrease the memory foot print.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk