Explain about C++ Pointers and new

I can think of only one significant area in which it looks like pointers are never going to go away for C++ programmers, at least not any time soon. When you use the new keyword, either to dynamically allocate an object or dynamically allocate a primitive data item (integer or floating-point), the keyword returns an address, which you normally assign to a pointer.int *p1 = new int;   // p points to a dyn. allocated integerOne thing I like about C++ is that, unlike Java, C#, and VB.NET, it recognizes no fundamental difference between primitive types and classes. Classes, in C++, are simply types that you create yourself, in effect extending the language.Therefore, you dynamically allocate and refer to an object—an instance of a class—in precisely the same way you’d dynamically allocate an integer:MyClass *p2 = new MyClass;   // p points to a dyn. allocated objectBut this syntax mandates pointer usage; I can see no safe way of coercing such a pointer value into a reference. You are stuck with pointers, at least in current, standard versions of C++. (Because, as shown earlier, pointers and references in function arguments usually have the same underlying implementation. It would be theoretically possible, I suppose, to trick the compiler into accepting one for the other, but don’t ever try that at home!)Interestingly enough, Java, C#, and VB.NET all use references in this situation, which is relevant to my learning problem that I mentioned at the beginning of this article. In these languages, you can declare an object variable (that is, a variable with class type), but it is always a reference. That means it “points nowhere” unless initialized with either (1) an object allocated with new or (2) the name of an existing object. Because references are used consistently in this context, they work just fine—as long as you understand how references work.There is one other reason why you will continue to work with pointers in C++. The use of pointers is deeply ingrained in the C++ standard library inherited from C. Many of the newer language features, such as range-based for and the items in the Standard Template Library (including the C++ string class) tend to minimize pointer usage, and in doing so present far fewer opportunities for you to inadvertently shoot yourself in the foot.And yet C++ will always support pointers because, despite their dangers and difficulties, there will always be that occasional op-system or device-driver writer that needs them.