Kelly O'Hair said the following on 06/19/10 01:23:
Just an aside comment.
I really hate import wildcards, seems so... inexact.
I side with the person who decided that wildcard imports were a good
idea for the language. I think explicitly listing every single type used
by a class as if it were a long list of C header includes is just wrong.
I can see how some tools might find it useful, but for the programmer
... yuck! If the IDE does it for you that helps but even then I don't
want to see that list regardless.
Just my 2c as I run out the door on vacation :)
David
I noticed that there are GPL utilities out there that could clean these
up for us,
making the import list exact.
One I found at http://www.javafaq.nu/java-article914.html, and I know
NetBeans and IDEs
have 'Fix Imports' options, I use them all the time. But if this could
be easily
batched... seems like something to think about.
Maybe that would be a good summer intern job of figuring out how to make
the imports
explicit, and also a scheme to maintain it?
What do you think? Is it worth it?
Maybe create a database too so people could run all the tests using a
specific class
or method? Just ideas...
-kto
On Jun 18, 2010, at 7:55 AM, Alan Bateman wrote:
This is another batch of updates to the regression tests to allow them
be run in jtreg samevm mode. This batch covers the java.io tests. As
expected, most of the issues are simply tests leaving files open,
causing problems for subsequent tests running in the same VM. There
are also several other random issues such as tests assuming the
working directory, one test assuming it will be defined by the system
class loader, and an issue cleaning up after a test that leaves a
hidden file.
The webrev with the changes is here:
http://cr.openjdk.java.net/~alanb/6962419/webrev/
With these changes (plus yesterday's batch to fix the serialization
tests) then all 305 java.io tests pass, for me, in both samevm and
othervm modes on all platforms.
Alan.
