[izpack-devel] OT: Java Imports in IzPack
Hal Vaughan
hal at thresholddigital.com
Sun Mar 12 20:02:42 CET 2006
On Sunday 12 March 2006 13:44, Julien Ponge wrote:
> Explicit imports are indeed recommended in most best practices.
I can understand that. What surprises me, though, is that I never saw
it done in any of the books I learned Java from and it is rarely done
in tutorials, examples, and articles. Seems many people are getting
lazy.
Actually, this is one of the habits working on custom panels and such
for IzPack has gotten me used to.
> The
> thing is that you can always start with a star import, and ask your
> favorite IDE to replace it with only the required imports.
I didn't realize that was a feature. I'm self taught (but used to
program in 6502 Assembler back in the 1980s), and for 3-4 years, my
idea of an IDE was Kate, a text editor in KDE that has a text window, a
file list window, and a console, so I had the console and text in the
same window. I'm still blown away by all the toys Eclipse has.
I just found the feature to do what you're talking about. So now I can
just use * for my imports and let Eclipse figure it out from there. I
like letting the computer do my work!
> Except
> that it makes your dependencies explicit, I think I read once that it
> speeds-up the compilation, but I am really not sure that (1) it is
> significant, and (2) that it is actually the case :-)
I'd have to agree that if it is the case, it isn't significant, at least
in the few tests I ran.
Hal
More information about the izpack-devel
mailing list