When To Use Reference Over Pointer and Vice Versa In C++

[@JayAnAm]

Nice, but a bit incomplete. Pointers are needed for:
* Accessing heap memory
* Datastructures that make use of null-pointers like linked lists or trees
* Functions or datastructures that come from libraries that demand the use of pointers

[@rahul-patil]

We can also access heap memory with reference.
Base& baseRef_B = *(new Base());
baseRef_B.print();
Base& baseRef_D = *(new Derived());
baseRef_D.print();
Please let me know if there are any drawbacks.
Thanks.

[@amiladrck]

He is covering your second point though. The third one is kind of obvious don't you think? :D

[@Ady2xp]

Good video as always! Thank you and keep the good job!

[@CppNuts]

+Ady2xp thanks dude.

[@anuragdogra6739]

Great video with infos. Keep it up.

[@CppNuts]

Thanks for appropriation!

[@iraqiaseed]

what is the main difference between the upcasting with reference to avoid slicing and run time polymorphism?

[@rahul-patil]

4:16. I tried achieving it in the *main* function creating an object on *heap* and it works.
*Any drawbacks or risks in this*?
Base& baseRef_B = *(new Base());
baseRef_B.print();
Base& baseRef_D = *(new Derived());
baseRef_D.print();
Thanks.

[@swatigupta6881]

Just want to ask we can store reference of derived class to base class and type caste it later when needed. What is better? Storing it as a reference and typecasting it. or Storing it as a pointer and typecasting it. or its the same and we can choose anyone?

[@Elliskid1995]

Thankyou… this was my last question about pointers finally answered

[@CppNuts]

Glad i could help

[@nithyanarayan8080]

Why its an error to use pointer in copy constructor?

[@CppNuts]

show me your code.

[@nithyanarayan8080]

#include
#include
using namespace std;
class base{
int x;
public:
base(int x1):x(x1){
;
}
base(const base &o){
x=o.x;
}
void print(){
cout

[@CppNuts]

I don't seeany problem in this code can you tell me where the actual problem is?

[@nithyanarayan8080]

My question is why we don't use pointer in copy constructor instead of reference?

[@sajit1988]

@@nithyanarayan8080 I am also searching answer for the same question for looooong,
what I see is, reference is safe..it ensure the data is valid..pointer doesnt ensure this..it can be NULL or invalid..

[@himanshu2487]

very knowledge rich videos
form where did you study all this ?
i want to learn more

[@Gurl975-b9o]

Can anyone please explain me copy constructor point

[@swatigupta6881]

can we type caste base class reference to derived class??

[@CppNuts]

It is safe to go up from derived class 2 base class but if you are coming from base class to derived class then you should know that base was once a derived then only you can convert.

[@swatigupta6881]

@@CppNuts Thank you so much.

[@swatigupta6881]

Just want to ask we can store reference of derived class to base class and type caste it later when needed. What is better? Storing it as a reference and typecasting it. or Storing it as a pointer and typecasting it.

[@CppNuts]

If you ask industries are heavily using pointer.
Pointers give more functionality than Ref, i mean ref have some restriction which pointer don't.
So that's y pointer is heavily used.
There can be other reason too, but i don't remember right now.

[@bangaruteja9020]

Good Video

[@CppNuts]

Thanks..

[@pramodkumarkar4500]

Sooper !!!!

[@CppNuts]

Thanks man!!