Unresolved external symbol on virtual function?

What's happening is that virtual Base::bar needs to be in the vtable of a Derived, since there's no Derived::bar I don't understand your comment about "client requirements when the server changes". I don't see how base/derived maps to client/server. They're two independent dimensions to me.

What's happening is that virtual Base::bar needs to be in the vtable of a Derived, since there's no Derived::bar. I don't understand your comment about "client requirements when the server changes". I don't see how base/derived maps to client/server.

They're two independent dimensions to me.

Thanks MSalters, that is pretty much the conclusion we have reached. It was also discovered that Other. Cpp was instantiating a Derived.

The factory pattern would be a good solution. The client-server reference comes in to play when one is developing a component comprising Base as an SDK to a client who implements Derived (and/or Other). By the server making a change to Base, the client's build will be broken until Derived is also modified.

Of course, good API developers will not make API changes that would disrupt a client's build. Therefore, it is good to know that changing a Base function to be virtual is such a disruption.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.