Re: [boost] [move] Reason for BOOST_COPY_ASSIGN_REF?

Subject: Re: [boost] [move] Reason for BOOST_COPY_ASSIGN_REF?
From: Chad Nelson (chad.thecomfychair_at_[hidden])
Date: 2010-04-21 10:08:26

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

On 04/21/2010 02:30 AM, Jeffrey Hellrung wrote:

>> I'm obviously missing some key concept, because very little of that
>> parses. I don't know of any efficient way to determine what that concept
>> might be, so here are some possibly-nonsensical questions to try to
>> scare it into view: [...]
> 
> If you look at the definition of the move-enabling macros, you'll see
> that a move-enabled class (under C++03) has the following member functions:

Thanks for the explanation. I think I see it now.

>> Let me rephrase the question. The current Boost.Move library has been
>> discussed on this list since at least January of 2009, and it's still
>> not approved. So how can I adopt anything regarding boost::rv if the
>> library that defines boost::rv might still not be available if/when my
>> library is ready for inclusion into a Boost release? Would I have to
>> bundle move.hpp with XInt in that case? Or yank out the move stuff
>> completely?
> 
> I guess you have a couple options. [...]

By the sound of it, it will probably be approved before XInt makes it to
review. So it may not be a problem, but again, thanks for the information.
- -- 
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/

iEYEARECAAYFAkvPBtoACgkQp9x9jeZ9/wQvcQCfWpldrf7Gc/sWvnhICDmQhWt+
4D0An2ybPGPHJhor2q84HfbbeO6BuY8R
=UtKW
-----END PGP SIGNATURE-----