to virtual or not to virtual

bobster · 2004-10-22T07:44:41

Hi, I have been unable to find a clear explanation of this in any of my documentation. If i declare an abstract base class (call it A) and a concrete class (say B) that is derived from A, should I always declare A's virtual functions as virtual in B also? what is the difference between: (declaring a function virtual in A && declaring that function non-virtual in B) and declaring it virtual in both? In the particular case of a virtual destructor for a base class A, I am unclear on whether the destructor of B should also be declared virtual, and what difference that would make. Any answers would be especially appreciated as I am currently doing this stuff on a test sheet for a job application 8|

For Beginners

Started by bobster October 22, 2004 05:52 AM

9 comments, last by Jolle 19 years, 6 months ago

Jolle

178

October 22, 2004 07:44 AM

Quote:Original post by Polymorphic OOP
Quote:Original post by Jolle
blablabla

That's not a true at all. Once a function is declared virtual in the base A, it is ALWAYS virtual whether you explicitly write virtual in child classes or not. It's entirely up to you whether or not to write virtual in B or C. The outcome is exactly the same.

Yeah, a quick check shows that you're correct... now I'll have to hunt down and burn whatever source that taught me that in the first place ;)

Sorry for lying to you bobster :/

to virtual or not to virtual

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

to virtual or not to virtual

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines