Adapt to Boost.Move

[viboes]

As suggested in the ML Boost.Thread should move to Boost.Move to implement move semantics emulation.

[viboes]

See also:

#2380 boost::move from lvalue does not work with gcc

#2501 upgrade_to_unique_lock doesn't compile on C++0x mode

#4521 Error using boost::move on packaged_task (MSVC 10)

#4705 C++03 Move Support Undocumented

#4711 Must use implementation details to return move-only types

#6141 Compilation error when boost.thread and boost.move are used together

#6174 [thread] packaged_task does correctly handle moving results

These tickets could be closed once the emulation is adopted and of course the problem disappears.

This is one is related but will need more modifications.

#5990 shared_future<T>::get() has wrong return type

[viboes]

See also #6222 Compile error with SunStudio: unique_future move

[Evan Wallace <onlyone@…>]

Version 0 of the patch to #6194

[Evan Wallace <onlyone@…>]

Sorry about the long delay.

I have attached a patch should fix this, as well as #2380, #2501, #4521, #6141, #6174 and #5990.

The patch is relative to 1.48.0. The patch does not incorporate any changes made to the trunk since 1.48.0, and also does not incorporate the fixes to #6174 and #5990 that were attached to those tickets by viboes (I had already fixed the problems independently, before noticing about the existence of those patches).

The attached patch is missing tests and documentation. I will send a longer description and justification of the changes to the mailing list.

[Evan Wallace <onlyone@…>]

Version 1 of the patch to #6194

[Evan Wallace <onlyone@…>]

The new patch should address most of the concerns raised in the mailing list so far. The patch is again relative to 1.48.0, and it is still missing tests and documentation.

[viboes]

Committed in trunk at revision [76543].

[viboes]

Committed in release branch at [78543]