Re: package importing conventions

1999-05-03 Thread Will Koffel
At 4:54 AM -0700 5/3/99, Troy Wu wrote: >I agree that one, large namespace is impractical (see C++ =), but >there are times when it's simply more convenient. Especially since C++ allows you to overload = and it is smart enough to not die at compile time. It just checks what types you have on eac

Re: package importing conventions

1999-05-03 Thread Michael Sinz
On Mon, 3 May 1999 04:54:48 -0700 (PDT), Troy Wu wrote: >That an import uses a wildcard can also be a strength. One of the >merits of Java lies in its maintainability. Without the ability to >import entire package, packages whose structures are being changed >(generated code is notorious for ha

package importing conventions

1999-05-03 Thread Troy Wu
On Mon, 3 May 1999, Michael Sinz wrote: >class layout of java. So yes, it's fine that you declared a >variable as: > >java.util.List foo; Actually, I feel that the real problem is that import lets you use a wildcard. That is, IMHO, the real design flaw in Java. If import requi