Packages

[kelvSYC]

If you put a class inside a package, can it access classes in its
parent package without an import statement (eg. class foo is in package
a and class bar is in a.subpackage - can bar access foo without an
import statement)?

 

[Brad BARCLAY]

If you put a class inside a package, can it access classes in its
parent package without an import statement (eg. class foo is in package
a and class bar is in a.subpackage - can bar access foo without an
import statement)?

Yes, but only if you fully-qualify the classname. This is true for
classes in _any_ package (not just a parent package).

Brad BARCLAY

 

[Harald Hein]

If you put a class inside a package, can it access classes in its
parent package without an import statement (eg. class foo is in
package a and class bar is in a.subpackage - can bar access foo
without an import statement)?

Packages don't have parent packages, there is no parent - subpackage
relation. The only thing the two packages

abc.def
abc.def.ghi

have in common are the first seven characters in the name.

Package names are mapped to file names in case the .class files and
resources are stored in a file system. In this case it happens by
"accident" that the abc\def directory becomes the parent directory for
abc\def\ghi. Still, the packages are not logically related.

You can access public classes of another package by importing the other
package, or by specifying the full package name.