[177] in java-interest
Re: non-public classes in packages
daemon@ATHENA.MIT.EDU (Arthur van Hoff)
Fri Jun 2 14:57:45 1995
Date: Fri, 2 Jun 1995 10:33:43 -0700
From: Arthur.Vanhoff@Eng.Sun.COM (Arthur van Hoff)
To: java-interest@java.Eng.Sun.COM
Hi Jeremy,
> > > If browser.ApplyButton is not public why should the importing
> > > browser.* cause a name conflict?
> >
> > Good point. This is probably a bug in the compiler. I'll take a look
> > at it. For now just the fully qualified name X.ApplyButton.
>
> Which brings up the more general point: do "public", "private", etc
> control access or visibility?
A private class should not be visible or accessible outside the package.
However, a private method or instance variable is visible but not accessible
outside the class.
Have fun,
Arthur van Hoff (avh@eng.sun.com)
http://java.sun.com/people/avh/
PS: For questions about HotJava and/or Java please use our
mailing lists java-interest@java.sun.com or hotjava-interest@java.sun.com
instead of mailing me directly. Thanks.
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
