A virtual function is a function which can be overridden in a child class. Now because that''s a horrible description, here''s some code to make it a bit clearer, in the context of an RPG-type game:

  class Monster{public:    virtual void attack();};class Ogre : public Monster{public:     void attack();};class Troll : public Monster{public:   void attack();};  

So, we have a base Monster class, and two derived classes which represent specific types of monsters. Each monster has a separate type of attack.

  Monster* currentMonster;currentMonster = new Ogre;currentMonster->attack();delete currentMonster;currentMonster = new Troll;currentMonster->attack();  

... and that''s what''s so special about virtual functions. You have a pointer to a Monster. You call the attack() function. But depending on what currentMonster actually points to, a different function will be called. If it points to an Ogre, the Ogre''s attack function gets called. If it points to a Troll, the Troll''s attack function gets called.

~~~~~~~~~~
Martee

Even though this thread has been up for a few hours, it has yet to garner a reply.

I would venture that this is the reason why: I made a similar post a few weeks ago titled "Virtual Functions? Inheretince? Why use them?". Quite a few people gave me very useful replies. Perhaps you should search for it.

-------------------------------
"A promise to a woman is just a lie that hasn''t happened yet."
-Mr. Floppy

I stand corrected

-------------------------------
"A promise to a woman is just a lie that hasn''t happened yet."
-Mr. Floppy

~~~~~~~~~~
Martee