26 Apr
2013
26 Apr
'13
8:43 p.m.
I have a prototype for boost.move integration done: http://codepad.org/O5LljVkn
From what I can tell, boost.move uses C++11 features if available, and if not, uses a C++03 work-around (slight overhead if boost.move is used). I tested with MinGW GCC 4.7.2 (-std=c++03 and -std=c++11) and VS2012. If no move constructor is available, the code correctly resorts back to copy constructors.
One bonus of going this route is there are no compiler feature macro checks required in boost.operators since boost.move already takes care of this.