Re: Disadvantage of using wildcards in import statement.

From:

Lew <noone@lewscanon.com>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 01 Aug 2009 02:03:02 -0400

Message-ID:

<h50lqn$kq6$1@news.albasani.net>

Stefan Ram wrote:

  I believe that ?Currency? should still refer to your local
  class, unless you write ?import java.util.Currency? without
  the asterisk.

Lew wrote, quoted or indirectly quoted someone who said:

This is resolved unambiguously in
<http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.5>

Roedy Green wrote:

It is? I know you are a much better language lawyer than average. How
do you infer that from the statements there?

Quoting the JLS chapter 7.5:

The example:

import java.util.*;

causes the simple names of all public types declared in the package java.util
to be available within the class and interface declarations of the compilation
unit. Thus, the simple name Vector refers to the type Vector in the package
java.util in all places in the compilation unit where that type declaration is
not shadowed (?6.3.1) or obscured (?6.3.2). The declaration might be shadowed
by a single-type-import declaration of a type whose simple name is Vector; by
a type named Vector and declared in the package to which the compilation unit
belongs; or any nested classes or interfaces.

It's the part about the type being declared in the same package or and nested
classes/interfaces shadowing the import-on-demand.

--
Lew