On 2020-08-11 10:07 a.m., Jeff Garland via Boost wrote:
Here's a sample of the warnings -- looks to me like the python case all the warnings come from detail - so for modes past c++11 I'd think unique_ptr could be used. A macro for python could allow users to override the removal and use auto_ptr in their code if they choose. And this problem is isolated to python and locale.
./boost/locale/localization_backend.hpp:116:59: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] ./boost/locale/util.hpp:180:28: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] ./boost/python/detail/is_auto_ptr.hpp:17:40: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] ./boost/python/detail/is_auto_ptr.hpp:17:40: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
Note that the usage in Boost.Python is already wrapped in `# if !defined(BOOST_NO_AUTO_PTR)` so in principle that code shouldn't be visible in C++14 and beyond. Hence my question. I'll investigate. Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...