Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 864693
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T09:31:12+00:00 2026-05-15T09:31:12+00:00

auto_ptr on wikipedia said that an auto_ptr containing an STL container may be used

  • 0

auto_ptr on wikipedia said that “an auto_ptr containing an STL container may be used to prevent further modification of the container.”. It used the following example:

auto_ptr<vector<ContainedType> > open_vec(new vector<ContainedType>);

open_vec->push_back(5);
open_vec->push_back(3);

// Transfers control, but now the vector cannot be changed:
auto_ptr<const vector<ContainedType> > closed_vec(open_vec); 

// closed_vec->push_back(8); // Can no longer modify

If I uncomment the last line, g++ will report an error as

t05.cpp:24: error: passing ‘const std::vector<int, std::allocator<int> >’ 
as ‘this’   argument of ‘void std::vector<_Tp, _Alloc>::push_back(const _Tp&) 
[with _Tp = int, _Alloc = std::allocator<int>]’ discards qualifiers

I am curious why after transferring the ownership of this vector, it can no longer be modified?

Thanks a lot!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T09:31:13+00:00Added an answer on May 15, 2026 at 9:31 am

    The closed_vec pointer holds the type const vector<ContainedType>. Because the type is const, you can’t call any methods on it that aren’t also defined as const (which means they don’t change internal data). Naturally push_back is non-const, as it changes the vector, so you can’t call it on a const pointer. It doesn’t really have anything to do with auto_ptr, you could accomplish the same with regular pointers:

    vector<ContainedType>* open_vec = new vector<ContainedType>();
    open_vec->push_back(5);
    open_vec->push_back(3);
    
    const vector<ContainedType>* closed_vec = open_vec;
    closed_vec->push_back(8); // Fails
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

std::auto_ptr is not allowed to be stored in an STL container, such as std::vector
As a followup to Class containing auto_ptr stored in vector , I believe the
I'm just getting used to smart pointers using std::auto_ptr. Assume that I want to
Seem to be having an issue with std::auto_ptr and assignment, such that the object
After reading Jossutis' explanation on auto_ptr from his STL book I've got a strong
Reference here That destructor will also implicitly call the destructor of the auto_ptr object.
std::auto_ptr is broken in VC++ 8 (which is what we use at work). My
Why is it wrong to use std::auto_ptr<> with standard containers?
If I declare a temporary auto deleted character buffer using std::auto_ptr<char> buffer(new char[n]); then
I am developing an auto-builder that will run a series of steps in our

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.