From: Andrey Semashev
[snip] I'm seeing lots of warnings about use of deprecated std::auto_ptr [snip]
... See... unlike Boost, most of the ordinary world still uses C++2003 and will
I wouldn't call it perfect. In the lack of rvalue references I would have preferred an explicit method to return a proxy that acts like rvalue reference. But that's offtopic.
The point is that semantics of auto_ptr makes it clear who owns what, it works well for more than a decade and of course well known to users.
Would you consider porting Boost.Locale to boost::movelib::unique_ptr from Boost.Move?
Note that you will have to switch at some point as MSVC developers are
planning to remove auto_ptr from the standard library at some point.
To be honest I'd prefer something simple and straight forward over rvalue simulation library. I'd rather grap an implementation of auto_ptr directly to Boost.Locale. To keep simple and clear. I just what to note - Boost.Locale can be compiled in C++11 mode and used in C++03 mode - without breaking binary compatibility - few libraries do it but I'd rather want to keep it that way. Artyom