Skip to main content

Auto Pointer: auto_ptr

Auto Pointer:

The C++ standard library contains a class template called auto_ptr, which is just a pointer like object that knows enough to delete what it is pointing to when the pointer goes out of scope. The auto_ptr class takes a pointer to a heap object in its constructor and deletes it in its destructor, freeing the user from responsibility of deleting the pointer.

Auto pointers should be used in a function with multiple exit points. So that programmer need not explicitly delete the pointer at multiple places.

e.g. In the example below, there are multiple exit points in the function, thus ideal case for using auto pointer.

# include

# include

# include

# include

vector* getList()

{

vector<>* pvNumbers = new vector<>;

int number;

cout<<"give the 5 numbers";

for( int i = 0; i <>

{

cin>>number;

pvNumbers->push_back( number );

}

return pvNumbers;

}

void checkValidity()

{

//this function will check the validity of the

//numbers given by the user. The number will be invalid

//if it is equal to 13.

auto_ptr<> > apvNumbers(getList());

//this pointer should be deleted in this function.

if( apvNumbers->size() == 0 )

{

return;

}

unsigned unSize = apvNumbers->size();

for( int i = 0; i <>

{

if( (* (apvNumbers.get()) )[i] == 13 )

{

cout<< " You have entered invalid number."<

return;

}

}

cout<< " All the numbers are valid."<

//As we are using auto_ptr we need not delete the pointer explicitly

//Otherwise we will have to delete the pointer at

//three places in this function.

}

int main()

{

checkValidity();

return 0;

}

Use auto_ptr in functions with multiple exit points, so that the pointer is deleted on exit from function.

Comments

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...