Virtual Functions in C++

Поділитися
Вставка
  • Опубліковано 12 лис 2024

КОМЕНТАРІ • 506

  • @greob
    @greob 7 років тому +267

    There's no such thing as "minimal impact" in my opinion, there's impact or no impact. I'd rather avoid impact altogether. :P

    • @TheCherno
      @TheCherno  7 років тому +725

      If you live your life without recognising levels of impact and absorbing some, you're not going to get anything done.

    • @greob
      @greob 7 років тому +81

      I was just kidding, but the topic of optimization in programming is very interesting to me. ;)

    • @DarkLevis
      @DarkLevis 7 років тому +102

      Some additional runtime costs are acceptable to make the COST of actually programming it smaller. And hay, people even use python to program which gives you a heavy runtime penalty compared to C/C++...

    • @kevycatminecraftmore7721
      @kevycatminecraftmore7721 6 років тому +1

      Interesting.

    • @vighnesh153
      @vighnesh153 5 років тому +30

      Let's say, I just touch your cheeks using a fingertip and then I slap you. Both are impacts. The first 1 will just hurt you mentally (some feeling of awkwardness) but the second 1 will hurt you both physically and mentally). You may ignore the 1st one and move on with your life, but you won't be able to forget about the second one for quite a while. I hope I have made my point.

  • @JuanPabloOrtizYax
    @JuanPabloOrtizYax 5 років тому +709

    Brief explanation of uncovered topics (yet) in this video:
    Since strings is not a primitive type of C++ we need to import the header
    #include
    To use string without namespace std is like this:
    std::string MyString("hello")
    This is equivalent to:
    std::string MyString = "Hello"
    Pointer instances:
    new keyword returns a pointer
    std::string* MyString = new std::string("Hello")
    And if is a pointer you access their properties with -> instead of a dot (.)
    std::cout length()

    • @michamarzec9786
      @michamarzec9786 5 років тому +35

      Thanks for explaining. Now it all makes sense.

    • @archsheep7772
      @archsheep7772 4 роки тому +10

      Thank you for your detailed explanation!

    • @carlosantoniogaleanorios4580
      @carlosantoniogaleanorios4580 4 роки тому +31

      Thanks, this was really helpful. There is one more thing that was not explained before (as far as I can recall). In the constructor of the player class, he uses a constant string "name", which he passes by reference (first, I don't understand why this has to be a constant or a reference) and then he goes on to add the colon and m_name(name). I think I have seen in some other tutorial series that this is the way to load a value into a constant but I am not sure now.

    • @allenguan6755
      @allenguan6755 4 роки тому

      thank u bro, love u every much

    • @nendo502
      @nendo502 4 роки тому +18

      So what's "Player(const std::string& name) : m_Name(name) {}" exactly? Could u give me a keyword of this stuff to search? I have no idea what it is and how to search it for details.

  • @milenkopizdic9217
    @milenkopizdic9217 4 роки тому +340

    For the newcomers, my suggestion would be to watch "stack vs heap memory in C++", "how to create/instantiate objects in c++" and "the new keyword in c++" before watching this.

    • @vikkio88
      @vikkio88 3 роки тому +7

      thanks man, this is exactly what I was wondering

    • @furki6449
      @furki6449 3 роки тому +1

      thx :)

    • @aniketnegi2642
      @aniketnegi2642 3 роки тому +1

      thanks man!

    • @rustyelectron
      @rustyelectron 3 роки тому +1

      Thanks a lot.

    • @Hoppitot
      @Hoppitot 2 роки тому +4

      also inheritance in C++ really clears up the class Player : public Entity

  • @luisantonioreyes9375
    @luisantonioreyes9375 4 роки тому +219

    My English captions: "my name is HMO and welcome back to my syphilis gloss series".

    • @Till27_Spence
      @Till27_Spence 2 роки тому +3

      This is fax, i just tried it 🤣

  • @undeadguy2
    @undeadguy2 2 роки тому +4

    Figured id give you a thumbs up your 30 second explanation of what a virtual function does explained what my teacher could not do in 2 hours. Appreciate it sir.

  • @nilsmelchert776
    @nilsmelchert776 6 років тому +26

    Beautiful set of tutorials. Probably the best I've seen so far for any programming language.
    I also like how it is divided into the different episodes that you can watch whenever you are only interested in a specific topic.
    Thank you for your time and please keep going like this!

  • @raoulbrigola5050
    @raoulbrigola5050 5 років тому +22

    By far the best channel on youtube to learn anything about c++! Thanks a lot cherno!

  • @MilindNikose
    @MilindNikose 3 роки тому +23

    To better understand his code, go through these topics first:
    1. String Class
    2. Initialisation list
    3. Arrow Operator
    4. New keyword

  • @jonnyreh001
    @jonnyreh001 2 роки тому +3

    You are the best Cherno. I am visiting your c++ series regularly. Basically when I run into a concept I need to get familiar with on the go :D

  • @bassbatterer
    @bassbatterer 5 років тому +178

    One of my lecturers actually went and dissembled the function calls for a Virtual function and for non-virtual functions for us to look at. The Normal function call executed 4 assembly instructions where as the Virtual function call executed 6, the additional 2 were dereferencing the pointer to the function pointer in the Vtable and then dereferencing the function pointer in the Class-specific function list. The overhead of 2 extra x86 instructions is next-to unnoticeable compared to the penalty of setting up a new stack-frame (which you have to do for both anyway) so the performance hit really in negligible.

    • @jonnywright8155
      @jonnywright8155 4 роки тому +5

      Excellent comment. I'm having an error now which mentions the vtable and I think I know what's going on now thanks to this explanation . Thanks!

    • @rutanshu85
      @rutanshu85 3 роки тому +2

      Thanks for sharing!

    • @CWunderA
      @CWunderA 3 роки тому +1

      Doesn't it matter how big your vtable is though?

    • @ronensuperexplainer
      @ronensuperexplainer 3 роки тому +12

      Dereferencing the function pointer can cost you 1000 instructions, because RAM has a high latency.

    • @petersansgaming8783
      @petersansgaming8783 2 роки тому

      @@ronensuperexplainer depends. Couldn't one develop a prefetcher for this problem to reduce memory latency?

  • @jonathangerard745
    @jonathangerard745 3 роки тому +5

    Virtual functions at first seemed harder than pointers for me... You've simplified it so elegantly... Thank you :)

  • @ishouldhavetried
    @ishouldhavetried 4 роки тому +3

    Let me tell you, I've been going to school for Software Engineering, and I have taken a bunch of different languages. Not a single one of them I really understood, just got it well enough to pass the class. But ever since I've found your CPP series, it's really helped, and I think I finally "get" it. This is the first language where I'm able to code without having to look up the solution 5 minutes into trying. Thank you for this series!

    • @jscorpio1987
      @jscorpio1987 4 роки тому +1

      I don’t know if it’s this guys videos that influence my feelings but I feel like C++ is the most intuitive programming language I’ve ever used. I feel like the newer higher level languages abstract things away to the point where they actually miss their goal of being easier, and wind up being much more confusing because there is so much going on behind the scenes that you never really know what exactly your code is doing.

    • @sripradpotukuchi9415
      @sripradpotukuchi9415 4 роки тому +1

      @@jscorpio1987 +1

    • @weiss588
      @weiss588 2 роки тому +1

      @@jscorpio1987 hell no

  • @PirateDion
    @PirateDion 3 роки тому +2

    Gotta say this video helped me understand virtual functions a lot more than anything else so far.
    Going to have to hunt down the other things that confuse me. I've been following a C++ tutorial app at work during breaks and such and these were stumbling blocks that undermined my whole understanding of polymorphism.

  • @work9167
    @work9167 3 роки тому +2

    This is short and beautiful, man! Please, continue doing what you do now

  • @FranciscoCrespoOM
    @FranciscoCrespoOM 4 роки тому +7

    Most of the time I've seen a tutorial about virtual functions/vtables it works pretty well to make some diagrams on paper about how it works because it's such an abstract concept that in general people, especially newbies, find a hard time trying to understand what's happening under the hood.

  • @serkanozturk4217
    @serkanozturk4217 2 роки тому +6

    Personal notes:
    - Virtual functions help us to override functions in subclasses
    - Normally, without virtual functions, when you call a fucntion, that funtion is called according to the type the variable is declared, not according to the real type that variable points to(see video)
    - Virtual function helps you to call the proper fucntion, not according to the declared type, but according to the actual type it points to
    - Override keyword is used to specify that that function overrides another func in base class(u don’t have to use though)

  • @RossYlitalo
    @RossYlitalo 4 роки тому +1

    Very nice explanation. Short and right to the point. It's easy to agree with your assessment that v-tables have such minimal cost that the inconvenience of not using them makes using them a no-brainer. Thank you very much!

  • @hamza.abdullah807
    @hamza.abdullah807 5 років тому +53

    Guests: That's a very nice sofa, how comfy is it to sit on..?
    Cherno: No, it's just for the Aesthetics, I sit on the ground.

  • @michaelkane1072
    @michaelkane1072 2 роки тому

    It is the luckiest moment in this year that i found these series right after i started learning cpp

  • @0xbitbybit
    @0xbitbybit Рік тому

    Haha loving the "is he going to be in focus or not?" game I'm playing watching through these videos 😂 such an epic series though mate, thanks!

  • @othmaneparadis1576
    @othmaneparadis1576 4 роки тому +1

    guys this is the hardest in c++ so dont quit

    • @dwivedys
      @dwivedys 5 місяців тому

      Thanks for that timely and apt reminder! You got this all of you!!

  • @thomashaug5086
    @thomashaug5086 4 роки тому +2

    Dude you are great at explaining these things. Probably won't ever see this comment but thank you. I don't write comments a lot but I am teaching myself c++ and I've watched several of your vids and they are awesome and extremely helpful. Thanks again!

  • @LunaFlahy
    @LunaFlahy Рік тому +1

    1. Virtual function: declared in the base class, which enables the derived object to use its override function.
    2. Override: declared after the function in the derived class. not required, but avoid misspelling the function name or overriding the non-virtual function in the base class.
    3.V Table : stores the virtual function in the base class to dispatch, which cost space, int * pointer to the override function.
    4. in specific embedded systems, using v table might impact the performance .

    • @immalkah
      @immalkah Рік тому +1

      Rewording content in summary form is actually a great way to learn and reinforce knowledge 👍🏽

  • @JohannesBergerSiroky
    @JohannesBergerSiroky 6 місяців тому +1

    In 2:10 an entity pointer is pointing to a memory area assigned to a player object. It will get converted this way: Entity *e = (class Entity*)p; Great video!

  • @jackthehammer2245
    @jackthehammer2245 7 років тому +3

    Thanks for your video. One thing I could add for virtual keyword is to add this keyword on destructor of the parent class to prevent memory leak when a derived class is deleted through the parent pointer.

  • @PerchEagle
    @PerchEagle 5 років тому

    Dude ! You are wonderful, you are smart not to explain unnecessary stuff. Explain the important things and other important related aspects ! wow ..

  • @fireball111121
    @fireball111121 3 роки тому

    Thank God for these videos. My professor is super chill, but he's so bad at explaining things. He reads the book at us and then explains things as though we already know it and moves way too fast and gets way too complicated.

  • @Mikerandria
    @Mikerandria 4 роки тому +1

    Thank you! You explained VTable so easily. I can continue my Reverse Engineering tutorials in peace now. Keep up the good work!

  • @wayneray9489
    @wayneray9489 2 роки тому +6

    This is really complicated for me a new learner.

  • @Fidelity_Investments
    @Fidelity_Investments 2 роки тому +7

    you kinda ran away at the beginning there. You've not gone over the Player(const std::string& name) : m)Name(name) {} syntax, nor the e->GetName() syntax. You kinda just left a lot of people in the dust there my guy.

  • @rahulpillai1271
    @rahulpillai1271 Рік тому +1

    6 years later and I am still waiting for your VTable Video Cherno. 😆 I love your series. Please link me to the vtable video if there is one.

  • @w3w3w3
    @w3w3w3 5 років тому +7

    So many new concepts in this video, I wish you would just explain them quickly lol. All the other videos have been perfect. Thanks though.

  • @laureven
    @laureven 5 років тому +49

    If I was new to this I would have struggled to understand. Your explanation is very good but it is impossible to pause the video to see all code to be able to imagine this scenario. It would be nice to have this simple code all on the screen and then You explaining it. In Your video, You jumping between screens and this create a lot of confusion for all newbies I imagine. Maybe a smaller font :) ..the point is If I explaining this to anybody I Print the example code on a single page and then explain, If I jump pages from declarations to the main function this is very confusing ...but this is just me ...Anyway I like Your videos Regardless :) Regards

    • @zaid4708
      @zaid4708 5 років тому +6

      ikr its confusing where he keeps on jumping everywhere i cant keep up

    • @froycardenas
      @froycardenas 5 років тому +3

      Certainly, this is not a topic for a newbie... virtual function is a complex feature of class heritance that I don't think there is an easy way to explain to people who have never coded anything in their life. This guy is obviously an expert and knows what he is talking about because he must have been programming for years.

    • @ashwinregi9215
      @ashwinregi9215 4 роки тому +1

      That's true! I kept on pausing the screen to get it

  • @yugantkadu8621
    @yugantkadu8621 4 роки тому +2

    Please make a video on V Table and Memory allocation. I have been watching C++ playlist, your videos are very good to get concepts more clear.

  • @danielketcheson1965
    @danielketcheson1965 2 роки тому +2

    This series
    Applies in 2022
    Meets the standards for my school's conventions (industry standards)
    Is more articulate and understandable than the "C++ For Dummies" series
    Has a loving/lovable character directing it
    I (with next to no rep or qualifications) award the Cherno with best C++'s best resource award
    I said it here
    Now I'm going to say it everywhere else.

  • @mockingbird3809
    @mockingbird3809 4 роки тому +1

    Excellent explanation. Something I'm looking for. Thank you so much.

  • @salpelter
    @salpelter Рік тому

    tysm! every topic you explain is so clear and simple

  • @rcookie5128
    @rcookie5128 7 років тому

    Good stuff. Knew and used virtual functions already and funnilly enough I already learned this morning about the word "override" (also spoiler alert: final and volatile classes/member functions :O so much to learn!).

  • @TheSim00n
    @TheSim00n 7 років тому +10

    Awesome video as always Yan. I know for the general use of virtual functions this video is absolutely enough, but I would love to see an explanation of how early and late binding comes into play with these functions and the concept of a vtable. Thanks!

    • @TheCherno
      @TheCherno  7 років тому +10

      Yes, that will be covered in the vtable video. Late binding doesn't _really_ exist in C++ since everything must be known at compile time, and the vtable essentially just allows dispatching to a number of preset values (that are contained in the table), not to _anything_ which would be the case with late binding.

    • @TheSim00n
      @TheSim00n 7 років тому +2

      Right on. Thanks.

  • @ProtonPhoenix
    @ProtonPhoenix 3 роки тому +2

    -> in c++ ~~~ An operator in C/C++ allows to access elements in Structures and Unions. It is with a pointer variable pointing to a structure or union. The operator is formed by using a minus sign, followed by the geater than symbol as shown below but bro we didn't reach union yet

  • @Grace-vg4hf
    @Grace-vg4hf 6 років тому +1

    I'm working on an assignment and this is so helpful, thanks so much!

  • @pascalladal8125
    @pascalladal8125 2 роки тому

    Hey Cherno! Got to say great channel to learn c++, awesome channel to get used to the australian accent!! :)

  • @Fallkhar
    @Fallkhar 5 місяців тому

    Excellent, just what I needed.

  • @unmeinks5907
    @unmeinks5907 2 роки тому

    this is virtually the best tutorial on youtube (:

  • @nunofigueira8691
    @nunofigueira8691 2 роки тому

    Its was a very good and technical explanation, thank you.

  • @afrikamatshiye735
    @afrikamatshiye735 6 років тому +10

    Wait wait wait... Why did I just understand virtual functions in one video. Dude you're good. Thanks man.

    • @karmaindustrie
      @karmaindustrie 5 років тому +3

      This is the C++ apocalypse. Probably one positive side effect of Chernobyl.

  • @higheredjohn8316
    @higheredjohn8316 6 років тому

    Thanks for this - excellent refresher, and I learned a few new tidbits! Keep these coming.

  • @systematicloop3215
    @systematicloop3215 7 років тому +19

    I don't know if I particularly like the fact that the override keyword comes after the function signature. I come from C#, so it's strange to look at.

    • @vertigo6982
      @vertigo6982 6 років тому +6

      You must unlearn what you have learned.

  • @vaiterius
    @vaiterius 2 роки тому

    thanks Cherno

  • @ankitjain3461
    @ankitjain3461 3 роки тому +6

    More than 3 years now, still waiting for VTABLE video 😆

  • @exoticcoder5365
    @exoticcoder5365 3 роки тому +1

    Super helpful gosh

  • @willd4686
    @willd4686 5 років тому

    Your videos are amazing tools for learning this stuff.

  • @jairoacosta8940
    @jairoacosta8940 5 років тому

    thank you, i always come back to reference your videos.

  • @oleholgerson3416
    @oleholgerson3416 6 років тому

    good videos, keep it up. so glad you dropped the backgroundmusic

  • @handlethissonny
    @handlethissonny 6 днів тому +1

    DUDE UR VIDEOS R FUCKING AWESOMETYSM

  • @Metachief_X
    @Metachief_X 4 роки тому

    Super easy explanation. Many thanks mate

  • @TheSunscratch
    @TheSunscratch 7 років тому +46

    What is the difference between
    Player(const std::string& name):m_name(name) {}
    and
    Player(const std::string& name) {
    m_name = name;
    }
    Is it some kind of syntactic sugar?

    • @TheSunscratch
      @TheSunscratch 7 років тому +2

      Lightslinger Deadeye many thanks for your explanation!

    • @TheCherno
      @TheCherno  7 років тому +86

      There's no _real_ practical difference between the two, however there is a difference. Since m_Name is a class member which has the type std::string (which is stack-allocated), it will actually be instantiated twice in your second example (firstly with an empty string, and secondly copied from the name parameter), but only once in your first example (via the constructor's intiailiser). Definitely going to be a video on this in the future. :)

    • @TheSunscratch
      @TheSunscratch 7 років тому +1

      TheChernoProject thanks :)

    • @BlackPhillip-sw8xf
      @BlackPhillip-sw8xf 7 років тому +2

      +TheSunscratch Also you cannot use the first approach if the data member is static.

    • @matteocampo1732
      @matteocampo1732 7 років тому +5

      Does the compiler (with -O2 or -O3 ) optimize it so that there is no difference eventually?

  • @AbdulMoiz-ho8rx
    @AbdulMoiz-ho8rx 2 роки тому +1

    Excellent

  • @mohamedabdul633
    @mohamedabdul633 4 роки тому

    After surfing the internet for more than 10 minutes, and this tutorial was much more helpful.

  • @per-axelskogsberg3861
    @per-axelskogsberg3861 3 роки тому

    This was perfect! Thank you 💕

  • @GenericPhantom1
    @GenericPhantom1 Рік тому

    Virtual functions are basically backups for functions. So it tells the complier that if a function is overwritten then it knows that it originally meant.

  • @notremonde1652
    @notremonde1652 5 років тому

    You a life saver. keep up the good work!

  • @mytech6779
    @mytech6779 2 роки тому

    In Bjarne's book he states the cost of a vtbl as two memory accesses plus the function call, exactly. The vtbl is just a collection of pointers to pointers.
    Two accesses is proportionally huge for some special cases and totally insignificant for others.

  • @uwu8750
    @uwu8750 7 років тому

    Hey. Thank you so much! Had been waiting for this :)

  • @greg6094
    @greg6094 7 років тому

    Cherno, you are an absolute legend!

  • @PflanzenChirurg
    @PflanzenChirurg 7 років тому +3

    Love u dude

  • @altSt0rm
    @altSt0rm 3 роки тому +2

    Genius level teaching.. 10/10

  • @shockwave1789
    @shockwave1789 4 роки тому +68

    After watching this I realised Java is so easy compared to cpp.

    • @jscorpio1987
      @jscorpio1987 4 роки тому +24

      On the flip side, the ease of Java comes at the expense of the level of control and optimization that C++ gives you. I started out with Java and now, after getting used to C++, Java just feels so limited.

    • @shockwave1789
      @shockwave1789 4 роки тому +1

      @@jscorpio1987 Java's strength is in enterprise application ,it's toolset and frameworks are perfect for that . Yes it doesn't have much control over small low level optimisation due to jvm ,but platform independence compensates it perfectly .

    • @ezshroom
      @ezshroom 4 роки тому

      @@jscorpio1987 I also started with Java. And, even now, I still prefer Java over C++ but I see the strengths of it too. For example, anything related to graphics in Java to me seems like it hasn't really been thought about too much. Mean, games built with it are (usually) a lot slower and even basic interfaces are difficult to make. With C++, there are many more libraries built to help with this. While these libraries are often ported to Java, it just doesn't feel complete.

    • @aryanparekh9314
      @aryanparekh9314 4 роки тому +2

      After looking at the sky I realized it's blue

    • @smileynetsmileynet7922
      @smileynetsmileynet7922 4 роки тому +4

      Me using java: Why isn't this applet working? It worked last time I used java!
      About 1.5 years ago...

  • @34sisantachhatoi34
    @34sisantachhatoi34 4 місяці тому

    Concise... Like always😊

  • @lesptitsoiseaux
    @lesptitsoiseaux 4 роки тому +2

    I can't say how useful your series has been. My son is twelve and is into robotics and programming and switching from python to C++. He loves your series and I'm playing catchup to help him though I'm the one lagging behind. Thank you, and let me know, if you read this, if you ever considered doing something about OpenCV or anything machine learning? :-D

  • @jasonsui9029
    @jasonsui9029 3 роки тому

    what a wonderful tutorial! Love it!

  • @Joshua-gu5nj
    @Joshua-gu5nj 6 років тому +4

    Your hair reminds me of that scene in There's Something About Mary. You know which one.

  • @cap-advaith
    @cap-advaith 2 роки тому +1

    player(const std:string& name):m_name(name){} // this is an example of initializer list

  • @shirinkoul
    @shirinkoul 2 роки тому +1

    I enjoyed the video :)

  • @SR-oy5ou
    @SR-oy5ou 3 роки тому

    you just summarized my 3 hours lecture in 5 minutes

  • @lali3049
    @lali3049 2 роки тому

    Great explanation

  • @AngelTaylorgang809
    @AngelTaylorgang809 4 роки тому

    awesome video man

  • @Recovered
    @Recovered 4 роки тому +7

    I've watched alot of your series, and it's really good, I've learned alot so thank you. BUT this video is waay too fast, I just couldn't follow it 😢

    • @reenamola2075
      @reenamola2075 3 роки тому +1

      yea he messed up with this video big time. he tried to be a hero and overcomplicate it too much

  • @tsvetomirdenchev1440
    @tsvetomirdenchev1440 6 років тому +2

    TheCherno, thank you for your great tutorials! Are you planning on making a tutorial on generic programming and C++ templates?

  • @Chillzn-yt
    @Chillzn-yt 3 роки тому +1

    Employer in the interview: "Where did you study?"
    Me: "The Cherno University..."
    Employer in the interview: "Where is that located?"
    Me: "UA-cam..."

  • @Dagrond
    @Dagrond 2 роки тому +3

    I was wondering why you used the x->object style instead of x.object but it turns out that x.object won't use a vTable. Baby steps for me I guess.

  • @TheIsWorld
    @TheIsWorld 4 роки тому

    Türkçe altyazı ekleyenin eline sağlık.
    Thanks to the contributor for the Turkish subtitles.

  • @dafid
    @dafid 4 роки тому

    Congrats, fellow hacker, i recognise you as one of them 'Non-pasters', have a nice journey hooking them VMT-s!

  • @TurtlesWithAutism
    @TurtlesWithAutism 4 роки тому +1

    Okay Cherno... we get it... we are dumb. You happy now?
    Guess I'll just have to watch more of your videos to understand these unexplained concepts, which I was going to anyways because you're the best teacher ever.
    :D

  • @LokeshKumar-os6ux
    @LokeshKumar-os6ux 4 роки тому

    you are genius

  • @Hope-kf1nl
    @Hope-kf1nl 5 років тому

    A+ video. Very helpful.

  • @manuelruiz9278
    @manuelruiz9278 9 місяців тому

    Nice video, thanks bro

  • @aritzolea6554
    @aritzolea6554 7 років тому +10

    A very basic question (coming from java).
    Why do you write Entity* e = new Entity()? Why do you add that pointer * ?

    • @TheCherno
      @TheCherno  7 років тому +17

      Because the *new* keyword dynamically allocates memory and returns a pointer to the address of that allocated memory, hence why we need a pointer type. Check out my video on pointers if you haven't already, and I will definitely be making a video on memory allocation in the future.

    • @edino1981
      @edino1981 7 років тому +4

      I will just add that in Java classes are by default reference types, while in C++ everything is value type, so if you need to refere to the same value, then you need to use pointers. So you can use same class definition as reference or value type. For example if you have new class Vector (position) , and you pass it to function as Vector (by value) or as Vector * ( as pointer only). If you embed Vector in Entity you can embed entire Vector or only a pointer to Vector.

  • @ManishSharma-fi2vr
    @ManishSharma-fi2vr 2 роки тому

    Thank You!!

  • @alexanderfitterling
    @alexanderfitterling 3 роки тому

    pretty cool! ... well explained.

  • @Gr0nal
    @Gr0nal 3 роки тому

    I thought things were going well, I thought I understood things, and then this episode just smashed my confidence into a wall. What the heck is going on xD
    I'm hoping I'll just understand this a bit better after watching future videos I guess... but "hoping I understand later" is a mistake I've made too many times.

    • @Gr0nal
      @Gr0nal 3 роки тому

      I get it now, after watching more videos ahead.

  • @choosyguytest719
    @choosyguytest719 5 років тому +39

    I dont get it... hard to understand at this point.

    • @loveboat
      @loveboat 5 років тому +13

      These videos started out so exceptionally great but it seems he has grown weary of this subject now, rushing through them and using unexplained code all the time.

    • @vertigo6982
      @vertigo6982 5 років тому +3

      Go review the video on Inheritance.. That should help you understand it better.

    • @woofelator
      @woofelator 5 років тому +2

      @@loveboat wat

    • @deletevil
      @deletevil 4 роки тому +5

      There is Zero problem with this video. If you don't get it then you haven't actually practiced inheritance enough to learn why we needed the virtual functions in the first place. Just watching videos will never get you anywhere in programming. You will have to actually write the code, test it with all possible conditions you can think of, try to do illegal stuff and then understand why it is not working, is the only way you can truly learn any topic.

    • @jerfersonmatos28
      @jerfersonmatos28 4 роки тому +1

      @@deletevil I think he is not refering to virtual functions. Cherno introduced many other subjects in this video without explaining them, but all these are explained in future videos, so the only thing to take out of this video is the type "Virtual" subject

  • @deleted_handle
    @deleted_handle Рік тому +1

    my head hurts why isnt this easier >_

  • @NGh_teh
    @NGh_teh 2 роки тому +4

    Hey Cherno. Thanks for the videos first. Can you explain the syntax you used in the player constructor? what is this specifically: m_name(name){ }. I know it sets the name to variable m_name but I have never seen this syntax before. Why you didn't do it in the body and the body is just empty? Can anyone explain to me? Second question. Sometimes in the formal parameters, you expect a pointer but in the actual parameters, you pass a normal data type like a string literal. Also in the body function where you are expecting a pointer, you just use that variable without dereferencing. I am confused by this. Can you help me with that?

    • @enes5345
      @enes5345 2 роки тому +6

      hey I hope you found answers your questions but this maybe helpful for someone else , for the first question:
      In c++ there is a way to initailize a variable with { } without using = operator , so for example int x{0} , y {10} (you basically did x=0, y=10;) and also you can use this way of initalization for constructors in this case ,
      Player(const std::string& name) :m_Name{name}{ } basically initalize m_Name to the value of name it is actually the same thing with
      Player(const std::string& name) { m_Name = name; }, depends on your style of coding
      for the second quesiton I think you mean this parameter in the Player constructor , (const std::string& name ) so here & says it is a referance to the variable not pointer , it is widely used for parameters to strings in order not to create a temporary string value and copying its value to it like
      void getName( string name) {m_Name = name; } because here you basically created a name variable and you passed a value to it like "Cherno" and you copy it to the m_Name, this means an extra garbage spaces right but if you use & then there wont be any name value created, so directly "Cherno" or , whatever you pass , it will be directly assigned to m_Name,
      I hope its clear and you can watch reference video or see more examples on it :)

    • @maolin7866
      @maolin7866 Рік тому +1

      @@enes5345 thank you!

    • @enes5345
      @enes5345 Рік тому +1

      @@maolin7866 you're welcome and also I am sorry I have learnt recently something new that I didn't know that in c++ initializing variables using initializer list( intiliazing variables after : ) is different than to initialize variables in the constructers body , when you initialize variables using initializer list what c++ do is it directly creates and initializes variables in the memory with the values that you have passed but doing this in the body of the constructers, c++ creates those variables in the memory and than assign them those values, this doesn't make much difference with intgrrs doubles or so but if you pass any object to the constructers like in copy constructers than using initializer list makes difference its faster as far as I know ( If you guys know sth diff pls tell us ) ,and one more thing initilazing vatiables using ( ) , and {} also different even in normal initialization like
      int a{}; different than int a(); again this might not make alot differencr for the int like variables it makes for objects creation , do in this way
      Point(string& name)
      : m_Name {name}
      {
      //Body
      }
      Thanks for your comment so that I could find a way to correct myself 😅🤗

    • @vickyzz4436
      @vickyzz4436 Рік тому +1

      @@enes5345 Thank you for your explanation!

  • @oraclematon9277
    @oraclematon9277 2 роки тому

    this is the best

  • @bartlomiejodachowski
    @bartlomiejodachowski 2 роки тому +2

    1:10 why is m_Name, class variable, used after : and with () like a function ?
    is : part of labda" notation ? and () funcional" casting/asigment ?

  • @naganrpin
    @naganrpin 4 роки тому

    Like the speed... Good.

  • @AE-yr6mo
    @AE-yr6mo 3 роки тому

    @The Chomo, Put your C++ tutorial series in order you queen.

    • @webstime1
      @webstime1 3 роки тому

      You really butchered the name

  • @sameeranjoshi3819
    @sameeranjoshi3819 3 роки тому +2

    @The Cherno when you say some people don't prefer virtual functions, what's the other option in that case?
    Is it CRTP ? Do you have a video on what to use if no virtual function?

  • @impe001
    @impe001 4 роки тому

    u save me dude thank you so much !!!!!!!