You will never ask again about pointers after watching this video!
HTML-код
- Опубликовано: 25 авг 2024
- In this video, I will teach you all you need to know about pointers in C++.
This video is aimed both at beginner and advanced programmers 💪!
Beginner: 0:56
Intermediate: 5:54
Advanced: 10:46
#cpp #programming #learncpp #gamedev
Also, check out how I handle memory management in C++! 💪:
• What I do to never hav...
Join my Discord 🤖:
/ discord
My Steam Game: Midnight Arrow 🎮:
store.steampow...
Join this channel if you want to support me 😻:
/ @lowlevelgamedev9330
Check out My Minecraft Clone 🌳:
• Minecraft clone
Full C++ Game Guide 🕹️:
• Make a C++ game FULL G...
Music:
Evan King - Booty Shake Robot
Evan King - Invisible Walls
/ contextsensitive
contextsensiti...
Minecraft soundtrack: C418 - Aria Math
Your teaching style is batter than most c++ RUclipsrs for beginners.
It is mostly accurate.
This is what I seen that needed a bit of correction:
Well technically arrays are not pointers and if you use them like pointers they decay
So don't say that an array is a pointer .
The size of it is not normally the size of pointer .
They can be referenced like :
T (&ref)[N]
And this can not be a pointer reference so they are not the same.
Additionaly :
When you make a function with array arguments it is a pointer to the elements.
unless the arguments is a reference .
You can actually see this in msvc:
auto p="";
auto&&a="";
The types are:
const char *,
const char(&)[1]
and some parts about void* ers can led to undefined behavior if you use the wrong type.
And Additionaly you may use new and delete on their own but the catch is that your code is not exception safe .
make sure that at least the delete is in some kind of destructor to make it safer .
In fact you can make a custom( template ) class to hold a lambda and run that on destruction .
This will be handy I promise.
yes it is true tho I think that's probably too much for a beginner 😂 but good points 💪
@@lowlevelgamedev9330 @lowlevelgamedev9330 yeah 😅 .
And that's probably why the cherno has more subscribers that Cppcon and c++weekly combined .
😂😅
aint the last one just std::unique_ptr ?
@@thepaulcraft957 it's not a replacement for unique ptr , this patern is more useful ,unique ptr just hides this work .
int* first;
let's goo first pointer of the video 💪
struct Comment {
//count
int likeCount = 0;
int dislikeCount = 0;
short replyCount = 0;
//date vars
short day;
short month;
short year;
//text
char* text;
char* user;
//bools
bool hearted = false;
struct Reply {
//count
int likeCount = 0;
int dislikeCount = 0;
//date vars
short day;
short month;
short year;
//string info
char* text;
char* user;
char* userReply; //only exists if you're replying to others
//bools
bool hasReplied = false;
bool hearted = false;
};
};
// i dont know if this would actually work but whatever
unsigned int* first;
Unsigned const short int* first;
constexpr unsigned long long* first = 1;
Beginner: 0:56
Intermediate: 5:54
Advanced: 10:46
thanks, I have to add it in the description 💪
8:08 i always got confused at arrow operator now i understood it thanks for this video😊.
glad to help 💪💪
Thanks for the video! This is a great video for an introduction to pointers!
I would like to add something to it though, like best practices, especially for beginners. Here's my take on it:
1. First of all never use *pointers*
2. If you need a dynamic memory, use *std::unique_ptr* instead for single ownership
3. In need of shared ownership? then look around your code, you probably structure your program badly
4. You absolutely need a shared ownership? use *std::shared_ptr* then
5. If you need a view to a memory/resource that you don't own, use a *reference* (borrowing)
6. If you need a view to a contiguous area of memory that you don't own, use *std::span* (*std::string_view* if it's a string)
7. Only if all the above not apply then you are probably okay using a *pointer*
Most of the time you want to use number 5 since dynamic memory allocation is not that common (always use the stack not the heap unless you need to).
make a video on memory allocation and smart pointers
yes it is comming 💪
@@lowlevelgamedev9330 WHEN?!?!!!??!?! I know you're doing it for free, but that's not an excuse for stalling. 😂😂😂😂 Thanks for sharing your knowledge in a useful way.
Learned a thing or two! Thank you for making this :D
glad to help 💪💪
Simple way to abstract pointers is all they are literal pointers, you’re pointing to a value. Say if I’m pointing at a cat, the pointer isn’t the cat but my finger itself.
good point, I like it 💪
When you know how variables work, you know how pointers work. Don't be too afraid of pointers.
yes true 💪
Thank you so much, super informative!
So one of my university courses this semester actually requires me to make a text-based game in c++. This is actually so useful
yo check out the first videos of my winapi series, they show exactly that 💪
Let's goo! Next make a tutorial video about making an MmoRpgFpsPointAndClickAdventureMetroidVaniaZeldaInspiredMinecraftCloneRogueSoulsLike multiplayer c++ game, pretty please?
good idea, that was my plan actually 💪😎
@@lowlevelgamedev9330 Yay!
Hey man, just asking whether you ever thought of making a video series teaching opengl, i really like the way you teach and think you're the perfect guy for this job
I might make some videos on the topic but I don't know if I'd do a full series, that takes a lot of time
the minecraft song in the beginner :D
good stuff 😌
nice, very cool
Edit: i want the smart pointer video!
ok noted, 💪
Great video, and i would love to see a tutorial on memory allocation : )
noted, third request already, I think I will make it 💪
How come you don’t use smart pointers?
GREAT Video. Absolutly great.
thanks 💪
"I don't use smart pointer", that must have triggered a lot of C++ developers.
yes I know 😂😂
So i have a one question about pointers and references
when should i use a pointers to pass some data to a function and when should i use references?
void fun(int* ptr)
void fun1(int& ref)
This is confusing because they are very similar besides some sytax sugar.
good question, so they do the same thing but a refference can't be null. The language forces you to refference it to something. So I use pointers in function arguments when it is something optional, and refference when it isn't optional
why dont you use smart pointers
I still don't get why people prefer using pointers when they do a bit of object-oriented... Maybe you'll tell us a bit more about this in your video about memory allocation 👍 I don't think I learnt something in this video, but it was explained very well, so congrats for "popularizing" this quite advanced concept, especially with these great metaphors!
first thing that comes to mind is copy size. moving 8 bytes is much cheaper than moving a 24 byte or more object for instance.
again, that's not a reason to do it, you can always make a refference and a new pointer if you want, pluss 24 bytes still takes no time to copy
Well I don't know either, those are the facts and I think people do it just out of poor habit :((
@@lowlevelgamedev9330 a reference is an underlying pointer :)
@@lowlevelgamedev9330 24 bytes isn't that much but in my project i have a single context struct that is probably hundreds of bytes big for Vulkan and it's passed to every function
i demand a video to understand what is the difference between coding and programming and how to understand programming like i have no idea how the gui works and how to get into game development .
and what the hell are algorithms and data structures and data bases dude 😭😭
my head is gonna explode with how much info i am having to deal with ,
for i in range(1000) :
print("i need help")
woomp woomp
Edit: its not that hard actually, i recommend watching Harvard CS50x, its a great online course that explains everything you need to get started with programming (btw, its just the harvard computer science lectures recorded, but its magnificent)
this is the exact channel for this, check out my full game guide in c++, or my videos about how to start or continue learning cpp or how to learn cpp for gamedev, I have several
@@lowlevelgamedev9330
thank you brother
you have no idea how much im thankful
its ok,
but you def. should explain the syntax (very shortly),
before beginning the intermediate explanation.
I know the syntax, just saw that you already used syntax in your pics before explaining it.
fair point, I'll be more carefull next time
@@lowlevelgamedev9330👍
I came here expecting some beginner stuff. Although i knew all of these, it really was an in-depth video about pointers. Specially things like funtion pointers that most beginners don't even know exist.
Another question that beginners ask is why arrays start from index 0, this could easily be added to when you talk about pointer arithmetic while accessing the array.
Overall a great video and something I'd recommend to people already familiar with the language incase they want to refresh their memory.
thanks bro 💪 I'm glad you liked it
Smart pointers..
... I knew all of this already
Is the information about the heap the same for C?
yes, that has to do with the os more than the programming language
@@lowlevelgamedev9330 thank you very much! so if i design functions in C to call by reference, should I use void add(int *i, int *j) hypothetically or can i use void add(int &i, int &j) just the same with better performance?
@@Gabezen101 c doesnt have references so you have to use pointers
int *second = &first;
haha
int **third = &second;
😂😂 epic
The last part was messy. I still don’t understand it.
5:51 negotiable*
8:14 reference*
thanks 😭 I'm bad at spelling
12 53 12 12
huh?
Say hello
say amongus 🔫💀
C is high level only assembly is low level
What about binary?
@@mihaelasimerea9700 also low😃
fair enough but for some people even c is too low level for them 😂
@@lowlevelgamedev9330 you replied to me 😳
@@lowlevelgamedev9330 yep