You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you read concrete classes its not always clear whether a member is
delibrately package local or left unspecified.
Members left unspecified can often be made private or even deleted
(checking for unused private members is simpler than unused package local
members)
Some members can appear that private is okay, however for performance
reasons may have been delibrately made package local. e.g. a member which
is accessed by an inner class can perform better if package local rather
than private (due to the use of accessor methods)
To address this I suggest a @package_local annotation to signify that a
member is explicity package local.
Original issue reported on code.google.com by [email protected] on 27 Jan 2009 at 5:06
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 27 Jan 2009 at 5:06The text was updated successfully, but these errors were encountered: