Overriding public virtual functions with private functions in C?

The problem is that the Base class methods are its way of declaring its interface. It is, in essence saying, "These are the things you can do to objects of this class When in a Derived class you make something the Base had declared as public private, you are taking something away. Now, even though a Derived object "is-a" Base object, something that you should be able to do to a Base class object you cannot do to a Derived class object, breaking the Liskov Substitution Prinicple Will this cause a "technical" problem in your program?

Maybe not. But it will probably mean object of your classes won't behave in a way your users expect them to behave If you find yourself in the situation where this is what you want (except in the case of a deprecated method referred to in another answer), chances are you have an inheritance model where inheritance isn't really modeling "is-a," (e.g. Scott Myers's example Square inheriting from Rectangle, but you can't change a Square's width independence of its height like you can for a rectangle) and you may need to reconsider your class relationships.

The problem is that the Base class methods are its way of declaring its interface. It is, in essence saying, "These are the things you can do to objects of this class. " When in a Derived class you make something the Base had declared as public private, you are taking something away.

Now, even though a Derived object "is-a" Base object, something that you should be able to do to a Base class object you cannot do to a Derived class object, breaking the Liskov Substitution Prinicple Will this cause a "technical" problem in your program? Maybe not. But it will probably mean object of your classes won't behave in a way your users expect them to behave.

If you find yourself in the situation where this is what you want (except in the case of a deprecated method referred to in another answer), chances are you have an inheritance model where inheritance isn't really modeling "is-a," (e.g. Scott Myers's example Square inheriting from Rectangle, but you can't change a Square's width independence of its height like you can for a rectangle) and you may need to reconsider your class relationships.

You do get the surprising result that if you have a child, you can't call foo, but you can cast it to a base and then call foo. Child *c = new child(); c->foo; // compile error (can't access private member) static_cast(c)->foo(); // this is fine, but still calls the implementation in child I suppose you might be able to contrive an example where you don't want a function exposed, except when you are treating it as an instance of the base class. But the very fact that that situation pops up would suggest a bad OO design somewhere along the line that should probably be refactored.

There's no technical problem, but you will end up with a situation where the publicly available functions will depend upon whether you have a base or derived pointer. This in my opinion would be weird and confusing.

It can be done, and very occasionally will lead to benefits. For example, in our codebase, we are using a library that contains a class with a public function that we used to use, but now discourage the use of due to other potential problems (there are safer methods to call). We also happen to have a class derived from that class which a lot of our code uses directly.So, we made the given function private in the derived class in order to help everyone remember not to use it if they can help it.

It doesn't eliminate the ability to use it, but it will catch some uses when the code tries to compile, rather than later in the code reviews.

It can be very useful if you are using private inheritance - i.e. You want to reuse a (customized) functionality of a base class, but not the interface.

No technical problem, if you mean by technical as there being a hidden runtime cost. If you inherit base publically, you shouldn't do this. If you inherit via protected or private, then this can help prevent using methods that don't make sense unless you have a base pointer.MSN.

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.