Re: Float.MIN_VALUE
Lew wrote:
Patricia Shanahan writes:
If that is really, really necessary, you will have to use
"java.lang.Float" any time that is what you mean in that package.
Stefan Ram wrote:
Another possibility is
import java.lang.Float;
once at the top of the source file.
Technically incorrect, but even if it worked it would be too ghastly.
It's much better not to hide java.lang classes, and so much easier. The
import does not solve the cognitive disconnect for the code maintainers
- only correct naming practices will do that.
The unqualified class name will cause a compile-time error due to the
conflict between the names, unless it's in the declaration of the local
Vector class itself.
I think it does work in all compilation units other than the one
containing the Float declaration.
"A single-type-import declaration d in a compilation unit c of package p
that imports a type named n shadows the declarations of:
* any top level type named n declared in another compilation unit of p.
* any type named n imported by a type-import-on-demand declaration
in c.
* any type named n imported by a static-import-on-demand
declaration in c. "
http://java.sun.com/docs/books/jls/third_edition/html/names.html#6.3.1
"import java.lang.Float;" is a single-type-import, so it shadows a top
level type Float in another compilation unit of the same package.
Of course, it would prevent simple name access to the in-package Float.
Patricia