package access

The protected modifier provides very weak protection compared to the private modifier, since it allows direct access to any programmer who is willing to go through the bother of defining a suitable derived class. Many programming authorities discourage the use of the protected modifier. Instance variables should normally not be marked protected. On rare occasions, you may want to have a method marked protected. If you want an access intermediate between public and private, then the access described in the next paragraph is often a preferable alternative to protected.

http://www.tanhuanyao.com   http:// tanhuanyao.com   http://www.bianshayao.com/   http://bianshayao.com/ You may have noticed that if you forget to place one of the modifiers public, private, or protected before an instance variable or method definition, then your class definition will still compile.If you do not place any of the modifiers public, private, or protected before an instance variable or method definition, then the instance variable or method can be accessed by name inside the definition of any class in the same package, but not outside of the package. This is called package access, default access, or friendly access. You use package access in situations where you have a package of cooperating classes that act as a single encapsulated unit. Note that package access is more restricted than protected, and that package access gives more control to the programmer defining the classes.If you control the package directory (folder), then you control who is allowed package access.