[203] in java-interest
Re: non-public classes in packages
daemon@ATHENA.MIT.EDU (Arthur van Hoff)
Tue Jun 6 19:26:13 1995
Date: Tue, 6 Jun 1995 16:12:06 -0700
From: Arthur.Vanhoff@Eng.Sun.COM (Arthur van Hoff)
To: java-interest@java.Eng.Sun.COM
Hi Edcuardo,
> | avh explains that private/public/protected for classes/methods works
> | like in C++: they affect accesability, not visibility.
>
> OK; not my prefered semantics, but there is an argument for it.
>
> | Then he says...
> |
> | private classes/methods/variables should not pollute the name space.
>
> I don't get this. It *is* polluting my name space. I cannot use the
> name of a method that is private because I might create an illegal ambiguity.
>
> Am I missing something?
The confusion is caused by the fact the current compiler does not
realize that some classes are private and should not pollute the
name space. This is due to a bug in the compiler. It will be fixed
in the next release. Sorry for the confusion.
Have fun,
Arthur van Hoff (avh@eng.sun.com)
http://java.sun.com/people/avh/
Sun Microsystems Inc, M/S UPAL02-301,
100 Hamilton Avenue, Palo Alto CA 94301, USA
Tel: +1 415 473 7242, Fax: +1 415 473 7104
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
