[boost] [move] Reason for BOOST_COPY_ASSIGN_REF?

Subject: [boost] [move] Reason for BOOST_COPY_ASSIGN_REF?
From: Chad Nelson (chad.thecomfychair_at_[hidden])
Date: 2010-04-20 22:32:16

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been studying Boost.Move, with an eye toward using it to
incorporate move semantics into the XInt library. Most of it looks
pretty straightforward, but I don't understand the reason for the
BOOST_COPY_ASSIGN_REF macro. If you already have a copy-constructor that
takes a reference, what does it give you?

Also, how close is it to being official? I'd like to use it, but if it's
not going to be accepted any time soon, I can't justify it.
- -- 
Chad Nelson
Oak Circle Software, Inc.
*
*
*
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvOY7AACgkQp9x9jeZ9/wRK1gCgvukakBrO37sCmHKwdhf9ebsI
rt8AmwYk3WwDZkUiUKKXb76Jeuh3n3w4
=8EHR
-----END PGP SIGNATURE-----