Thread: Protected purely virtual function

Hi,

Trying to generalize behaviour of a set of classes and to supply them with decorators, I'm implementing an abstract interface containing the common functions.

Now all my classes have a 'protected' member function "Update()" , which I thus make a protected purely virtual function in my base class.

Does this make sense ? I've seen something written on this, but I forgot where and what they said.

I can think of some polymorphic call-back, but this is not the way the function is used. Perhaps I'll just make it a public function? This will not have a negative impact on the code.

Thanks a lot for your answers !

Mark

Where will that function be called?

Code:

A::Update()

will only be called in A's member functions.

>> will only be called in A's member functions.
Then you can make it private.

It can still be virtual. If you want derived classes to have the opportunity to override it with different code. But if you're only calling it from A then you should make it private in A.