Hi Robert, >> "Once virtual, always virtual", i.e., it isn't necessary to add >"virtual" to >> any overridden virtual functions, and in fact it's not possible to >> "unvirtualize" once virtualized. I do try to maintain them as a >stylistic >> convention, but even I fall short sometimes ;-). Thanks for patching >that. > >My understanding is that this is not 100% the case. Or more >pedantically - in a class derived from a a class with virtual >functions, >those virtual functions wil get overriden, but if not declared virtual >themselves, any further derivations will not. I believe that the >technique of doing this to allow inlining of code calling references to >an object is called 'final classes'.
Sorry, Gary is right. See 10.3.2 of the standard. Regards, Jörg