Import java.io.* problem

Why doesn't "import java.io.*;" import FileReader and FileWriter? It seems to do so for other classes.

Unless I explicitly import FileWriter (ie: with "import java.io.FileWriter;"), the code below gives the following compiler errors:

ImportTest.java:8: cannot find symbol
symbol : constructor FileWriter(java.io.File)
location: class FileWriter
FileWriter fw = new FileWriter(f);

ImportTest.java:9: cannot find symbol
symbol : method close()
location: class FileWriter
fw.close();

Code:

---

import java.io.*;

class ImportTest
{
        public static void main(String[] args) throws IOException
        {
                File f = new File("Test.txt");
                FileWriter fw = new FileWriter(f);
                fw.close();
        }
}

---

I could use java.io.File, java.io.FileWriter and java.io.IOException but I'm puzzled as to why the import doesn't appear to be working as I expect it to.

I'm working through examples in a book and the code above is a stripped-down version of the example in the book which gives the same errors.

What have I missed?

Works for me, not sure what the deal is.

However...

You should import your classes explicitly. Importing * (everything) increases compile time a great deal. A good IDE (NetBeans, Eclipse) will do this for you automatically.

Quote:

---

Originally Posted by quad64bit

Works for me, not sure what the deal is.

However...

You should import your classes explicitly. Importing * (everything) increases compile time a great deal. A good IDE (NetBeans, Eclipse) will do this for you automatically.

---

Thanks for your help. I'm glad it works on your system, I was beginning to doubt what I thought I knew.

It turns out I had a file "FileWriter.java" in the same location as my example code. :o Compiling with -verbose showed an import from "./FileWriter.java" rather than the same location as the other classes.

Can't think how I managed to create a class with the same name as an existing one but it's useful to know that the compiler chooses that over the built-in classes.

I'll have a look at the IDE's you mentioned, I'm still on text editors.

that's why you should use packages :)

Well, one reason at least