Question

Possible Duplicate:
Why would you ever want to allocate memory on the heap rather than the stack?

Test2 *t2 = new Test2();
t2->test();

Test2 t3;
t3.test();

Why would I want to create a pointer object of type Test2? Why not just do non pointer version of Test2? Why would I want to do pointer objects?

Found answer here:

• Why would you ever want to allocate memory on the heap rather than the stack?
• When is it best to use a stack instead of a heap and vice versa?
• When to use “new” and when not to in C++?
• When should I use the new keyword in C++?
• Proper stack and heap usage in C++
• Stack, Static and Heap in C++

Answer 1

The reasons to use dynamic storage include (but probably not limited to)

1. Manual control of the objects lifetime – the object will live until you explicitly destroy it
2. Creating as many objects as necessary, when the final number of objects is only known at run-time (like number of nodes in a tree or number of elements in an array).
3. Run-time control of the object’s type (like actual type of polymorphic object).

When it makes no difference, it is always better to create the object using your t3 method. Don’t use dynamic memory unless you have to. But sometimes you really have to (see the reasons above).