Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: Java Language
Expertise: Beginner
Feb 1, 1999



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Access Modifiers

When should I make member variables protected and when should I make them private? Is it a good practice to ignore protected variables? It seems to me that most of the time, you don't want your subclass to be able to modify the member variables of the super class.

In general, any member variable that you do not want another class to access should be private. But it is not wise to generalize about when to use given access modifiers. What access modifier you use for a class member variable depends on your overall design framework. If a class is intended to be subclassed, you may or not want to make some of its variables and methods protected. The protected access modifier will allow subclasses to access the method or variable directly. This can be very desirable when you want subclasses to be able to modify behavior that you don't want to be publicly accessible. Similarly, default access is desirable when you want other classes in a package to access a class's method or variable, but you don't want classes outside of the package to have the same access. You just have to think carefully about the purpose of a class and how it will be used before you decide which access modifiers to use.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date