I came across a question while taking iKM test. There was a base class with two abstract methods with private access specifier. There was a derived class which was overridin
It is allowed, in both directions (ie, from private to public AND from public to private).
On the other hand, I would argue it does not break the IS-A relationship. I base my argument on 2 facts:
Base& (or Base*) handle, you have exactly the same interface as beforepublic and calling the private method directly anyway: same effect with more typing