|What is wrong in this code of c++|
Apart from the misspelling of private and protected? (the capital P would confuse the compiler!)
|Why we not go for private and protected Inheritance in c++ ?|
They are not used very often as there are normally better ways to achieve the same aim.
As you no doubt know, public inheritence is about is-a relationships. But this relies on the derived class inheriting the interface (i.e. public methods) so the outside world can see the class behaves like its parent class or classes.
Neither private nor protected inheritence add to the the public interface of a class, so they can not be used to inherit bevaviour, only implementation. That is, they represent an (e.g.) implemented-using relationship.
As you're just using the code internally, there's usually no need to inherit. Instead you can use composition (i.e. you have a class member which does the work), which is cleaner from an object pointed view as it has looser coupling.
There are cases when private inheritence is better than composition (as it makes things simpler), or is actually required, but they are the exceptions to the general rule.
This article discusses the issue, with examples of when non-public inheritence is useful:
Uses and Abuses of Inheritance, Part 1
See item 34 "Prefer composition to inheritence" in the book "C++ Coding Standards" by Sutter and Alexandrescu