On Wed, 2002-11-06 at 06:55, Tim Funk wrote:
> In case you weren't joking ...
>
> It can easily break compatibility if someone introduces a new class with
> the same class name as another class in a different package.
IMHO, the more important reason to not use "import xx.*" is because it
is harder for a developer to figure out where a class is coming from...
So I see it as a code readability issue.
Cheers,
-bob
>
> ex:
> import foo.*; /* has class A */
> import bar.*; /* has class B */
>
> class Foo {
> A a;
> B b;
> }
>
> Imagine time going by and another developer creates another class called
> A in the bar package. The code above will not recompile because of the
> abiguous class name.
>
> -Tim
>
>
> Costin Manolache wrote:
> > BTW - what's evil in import * ? I never understood.
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
