E2316 auto_ptr is not a member of std

[Dan Quinn]

Where did std::auto_ptr go?

[Duane Hebert]

Post by Dan Quinn
Where did std::auto_ptr go?

Is it not still in <memory>?

[Vladimir Grigoriev]

Post by Dan Quinn
Where did std::auto_ptr go?

As it was already said auto_ptr conceals itself in <memory>. However every
std container knows where auto_ptr conceals itself. So if you have, for
example,

#include <vector>

when you do not need to include <memory> though you may include it
explicitly to underline that you use auto_ptr youself..

Vladimir Grigoriev

[Chris Uzdavinis (TeamB)]

Post by Vladimir Grigoriev

Post by Dan Quinn
Where did std::auto_ptr go?

As it was already said auto_ptr conceals itself in <memory>. However every
std container knows where auto_ptr conceals itself. So if you have, for
example,
#include <vector>
when you do not need to include <memory> though you may include it
explicitly to underline that you use auto_ptr youself..

I'd suggest that if you need auto_ptr, for example, that you *always*
include the header that is defined to provide it, regardless if it
just-so-happens to be pulled in elsewhere.

It's *never* a good idea to needlessly add dependencies on
implementation deails.

[Vladimir Grigoriev]

I agree.

Post by Chris Uzdavinis (TeamB)

Post by Vladimir Grigoriev

Post by Dan Quinn
Where did std::auto_ptr go?

As it was already said auto_ptr conceals itself in <memory>. However every
std container knows where auto_ptr conceals itself. So if you have, for
example,
#include <vector>
when you do not need to include <memory> though you may include it
explicitly to underline that you use auto_ptr youself..

I'd suggest that if you need auto_ptr, for example, that you *always*
include the header that is defined to provide it, regardless if it
just-so-happens to be pulled in elsewhere.
It's *never* a good idea to needlessly add dependencies on
implementation deails.
--
Chris (TeamB);