Boost logo

Boost :

Subject: Re: [boost] [move] Library uploaded to sandbox
From: Christian Holmquist (c.holmquist_at_[hidden])
Date: 2009-02-17 20:33:20

> Anyway, my opinion is that we need some move library, better now than later
> even if it's too basic, so that we can unify all redundant move emulation
> that we already have in boost libraries. I hope this is a step in the right
> direction.
I've followed the discussions about move emulation because I badly need it
(without waiting for c+0x), and I've looked at the solutions in
Boost.Interprocess many times trying to reuse portions of it in my own code.
However, it takes careful crafting to get it done right, and I've been
worried about not being able to cover all test cases. Horrible things
happens if code compiles that shouldn't or objects are not moved as

The macros provided in your Move emulation library is exactly what I was

Used with move-aware containers where I can put move-aware homegrown objects
would be extremely useful, immediately.

If the updated versions of Interprocess and Intrusive are somewhat
compatible with Boost 1.35 (I don't dare to upgrade to 1.38 at this time),
I'd like to try out the library for production code (Windows, 64bit). I
could probably devote a machine for regressiontests as well for my platform,
if that helps.


Boost list run by bdawes at, gregod at, cpdaniel at, john at