CODEWITHSUNDEEP
java
jmasterx
jmasterx

Reputation: 54103

What are variables without public, private or protected declared as?

If instead of:

private JButton theButton;

I define a field like this:

JButton theButton;

What is the difference?

Upvotes: 42

Views: 51971

Answers (4)

Joakim
Joakim

Reputation: 2142

Here's a useful overview showing access permitted by each modifier:

Modifier Class Package Subclass World
public Y Y Y Y
protected Y Y Y N
no modifier Y Y N N
private Y N N N

The first data column indicates whether the class itself has access to the member defined by the access level. As you can see, a class always has access to its own members. The second column indicates whether classes in the same package as the class (regardless of their parentage) have access to the member. The third column indicates whether subclasses of the class declared outside this package have access to the member (i.e. classes that extend this class). The fourth column indicates whether all classes have access to the member.

Source (Oracle)

Upvotes: 6

Kevin Carrasco
Kevin Carrasco

Reputation: 1052

In Java there are public, protected, package (default), and private visibilities; ordered from most visible to the least.

If you do not specify it, by default the visibility is package.

package mytest.myvisibility;

public class MyClass
{
    public int myPublicInt; // visible to all
    protected myProtectedInt; // visible to subclasses of MyClass and to other members of the mytest.myvisibility package
    int myPackageInt; // visible only to other members of the mytest.myvisibility package
    private int myPrivateInt; // visible only to MyClass objects
}

Upvotes: 46

Iton Sandal
Iton Sandal

Reputation: 25

same as static function on c. only visible on the same file.

Upvotes: -1

Ed Staub
Ed Staub

Reputation: 15690

Package. They're visible to other classes in the same package.

FWIW, I usually use my own no-op @Package annotation on these, just to make it clear that I know what I'm doing - that I didn't just forget something. Even though it's the default, package access is probably used less in high-quality code than any of the other three possibilities - with one big exception:

In some styles of unit testing, it's desirable to be able to get access to methods or fields that are normally private. One way to provide access is to set them to package access, and put the unit test class in the same package (but usually in a different "test" directory tree). Some developers think that this is bad practice - that in general, it's bad to use private (or package-for-testing) methods in tests.

Upvotes: 53

Related Questions