[174] in java-interest
Re: non-public classes in packages
daemon@ATHENA.MIT.EDU (Jeremy Fitzhardinge)
Fri Jun 2 13:47:07 1995
From: jeremy@sour.sw.oz.au (Jeremy Fitzhardinge)
Date: Fri, 2 Jun 1995 14:09:27 +1000 (EST)
To: java-interest@java.Eng.Sun.COM
> > 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?
J
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
