Auto_ptr 是否已弃用？

  1. Auto _ ptr 会在传入的 C + + 标准中被弃用吗？
  2. 所有权转移是否应该使用 only _ ptr 而不是 share _ ptr？
  3. 如果独特的 _ ptr 不在标准中，那么我是否需要改为使用 share _ ptr？
46731 次浏览
小开
最佳答案

UPDATE: This answer was written in 2010 and as anticipated std::auto_ptr has been deprecated. The advice is entirely valid.

In C++0x std::auto_ptr will be deprecated in favor of std::unique_ptr. The choice of smart pointer will depend on your use case and your requirements, with std::unique_ptr with move semantics for single ownership that can be used inside containers (using move semantics) and std::shared_ptr when ownership is shared.

You should try to use the smart pointer that best fits the situation, choosing the correct pointer type provides other programmers with insight into your design.

小开

Yes, as of today auto_ptr will be deprecated in C++0x and you should use unique_ptr instead. From the latest draft standard (n3035), section D.9

The class template auto_ptr is deprecated. [ Note: The class template unique_ptr (20.9.10) provides a better solution. —end note ]

Until the standard is ratified, it's always possible that the committee will revise this decision although I feel that is unlikely for this decision.

小开

No, it isn't deprecated. It may be, if C++0x ever gets accepted. And it will realistically always be supported. I don't believe that any deprecated feature has ever been dropped from real-world C++ implementations.

小开

Not only auto_ptr is deprecated in C++11 (D.10, page 1228), it will also be deleted in a future version of C++:

Adopted N4190, and actually removed (not just deprecated) several archaic things from the C++ standard library, including auto_ptr, bind1st/bind2nd, ptr_fun/mem_fun/mem_fun_ref, random_shuffle, and a few more. Those are now all removed from the draft C++17 standard library and will not be part of future portable C++.

Another document about it: Programming Language C++, Library Evolution Working Group - Document N4190, if you want more information.

You can convert any code using auto_ptr automaticaly, by using unique_ptr instead:

Any code using auto_ptr can be mechanically converted to using unique_ptr, with move() inserted whenever auto_ptr was being "copied".


提交答案