Not much of an oversite at all I would gather...just have to think about
how you are coding a bit more..Careful is good when you are coding.
Cheers
J.
At 07:31 AM 5/3/99 -0400, Michael Sinz wrote:
>On Sun, 2 May 1999 20:04:19 -0400, Will Koffel wrote:
>
>>The java.awt.List and java.util.List conflict you have found is
>>in my opinion a VERY unfortunate oversight on the part of Sun.
>>It's one example of some lack of coordination in designing the
>>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 required fully qualified names at all times things
>would be much better. As it is now, many people import the world
>which makes the packages basically useless (everything is mushed
>together into a single name space) The nice thing about packages
>is that you can have the same class name (due to whatever reasons)
>in multiple packages and not have to give each one a strange name.
>(Why have to make Jfoo, Nfoo, etc., when it really is a foo?)
>
>
>Michael Sinz -- Director of Research & Development, NextBus Inc.
>mailto:[EMAIL PROTECTED] --------- http://www.nextbus.com
>My place on the web ---> http://www.users.fast.net/~michael_sinz
>
>
>
>----------------------------------------------------------------------
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
