Templates are all about the compiler generating code at compile-time. Virtual functions are all about the run-time system figuring out which function to call at run-time. Once the run-time system figured out it would need to call a templatized virtual function, compilation is all done and the compiler cannot generate the appropriate instance anymore. Therefore … Read more
When an object written in C# is constructed, what happens is that the initializers run in order from the most derived class to the base class, and then constructors run in order from the base class to the most derived class (see Eric Lippert’s blog for details as to why this is). Also in .NET … Read more
Calling virtual functions from a constructor or destructor is dangerous and should be avoided whenever possible. All C++ implementations should call the version of the function defined at the level of the hierarchy in the current constructor and no further. The C++ FAQ Lite covers this in section 23.7 in pretty good detail. I suggest … Read more
Here is how I understood not just what virtual functions are, but why they’re required: Let’s say you have these two classes: class Animal { public: void eat() { std::cout << “I’m eating generic food.”; } }; class Cat : public Animal { public: void eat() { std::cout << “I’m eating a rat.”; } }; … Read more
yes, a PVF can have parameters. virtual void playCard(Player enemyPlayer) = 0; here = 0 (is not assigning), Simply we are informing to compiler that function will be pure and does not having any body(where its declared, in that class), but it can have parameter. From the n4659 C++ standard A pure virtual function need … Read more