boost  

[boost] Re: memcpy_copyable<> and memcpy_moveable<> type traits

David Abrahams
Tue, 26 Aug 2003 16:27:18 +0000

"Peter Dimov" <[EMAIL PROTECTED]> writes:

>> I guess there is no equivalent to memcpy_moveable: but it looks rather
>> dangerous, what state is the original object left in afterwards etc?
>
> None. There is no original object after the move, only raw storage.

...which is a different meaning from move in our move proposal

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost