Mastering C++ pointers: the pros and cons of (raw) pointers | pointer usage with const

[@olegonka8801]

Крутий контент! Для початківців класне відео

[@CodeForYourself]

Дякую! Сподіваюсь далі підуть відео також для тих "хто вже вміє" 😉

[@Anton-vu1ou]

Great video! As always, high quality and quite detailed!

[@CodeForYourself]

Glad you enjoyed it!

[@marwanzaghloul6065]

Great video, thank you!

[@CodeForYourself]

My pleasure!

[@bsdooby]

`east const` vs `const west`: the geographic orientation represents the type. E.g., "int \*const ptr" [ptr cannot be reseated], or "int const\* ptr" [ptr cannot change the value it is pointing to]; backslash added to show the star character.

[@CodeForYourself]

Yep, pretty much

[@Pedro-jj7gp]

Nice video! Why is the int* 8 bytes instead of 4 at 1:30?

[@CodeForYourself]

@@Pedro-jj7gp that’s just the way it usually is on most modern systems: any pointer is 8 bytes. In the end this has to do with being able to address enough places in the memory if this makes any sense. That being said, other systems could theoretically have it be smaller or larger. Does this answer your question?

[@Pedro-jj7gp]

@@CodeForYourself It does, but I'm a bit confused as I was watching some other videos about vtables and they showed the vpointer taking up 4 bytes... I guess it could just be on that system.

[@CodeForYourself]

@@Pedro-jj7gp it might be. But you can always check it on your system too. I’ve only ever seen 8-byte pointers on every system apart from really non-standard embedded boards. 🤷‍♂️

[@Pedro-jj7gp]

@@CodeForYourself Yup, you're right! I just checked using sizeof() both for a regular int* and a vpointer using reinterpret_cast() and both are 8 bytes. The video in question was 12 years old, maybe it was a 32-bit machine

[@CodeForYourself]

@@Pedro-jj7gp sounds like a 32 bit system indeed. Glad that it makes sense now 👌