From the Java Language specification:
The access modifiers protected and private pertain only to member classes within a directly enclosing class declaration
So yes, the private and the protected modifiers are not allowed for top level class declarations.
Top-level classes may be public or not, while private
and protected
ar not allowed. If the class is declared public, than it can be referred to from any package. Otherwise it can only be referred to from the same package (namespace).
A private top level classes wouldn't make much sense because it couldn't be referred to from any class. It would be unusable by definition. private
is OK for member classes to make a class referrable to only it's enclosing class.
A protected member class can be referred to from (1) any class of the same package and from (2) any subclass of the enclosing class. Mapping this concept to top level classes is difficult. The first case is covered by top level class with no access modifiers. The second case is not applicable for top level classes, because there is no enclosing class or something else from a different package with a special relation to this class (like a subclass). Because of this I think, protected
is not allowed because it's underlying concept is not applicable for top level classes.