----- Original Message ----- From: "Chad Nelson" <chad.thecomfychair@gmail.com> To: <boost@lists.boost.org> Sent: Saturday, March 27, 2010 6:24 AM Subject: Re: [boost] New Boost.XInt Library, request preliminary review
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This disables the copy-on-write optimization that the library uses by default [...]
I'm not convinced that integers should be COW. What situations do you forsee where COW would be helpful but move semantics wouldn't suffice?
As described on the rationale page of the documentation, the primary reason I'm using copy-on-write is that move semantics aren't widely available yet. Portability is one of my primary goals, and while I've seen references to a move-semantics-emulator in Boost, I've also seen suggestions that it relies on the compiler to somehow recognize it. That doesn't sound fully portable to me.
Please could you be more explicit. Do you know some compilers on which Boost.Move doesn't works? Best, Vicente