Why java.io.File doesn't have a close() method

2019-01-10 13:38发布

问题:

While java.io.RandomAccessFile does have a close() method java.io.File doesn't. Why is that? Is the file closed automatically on finalization or something?

Thanks!

回答1:

The javadoc of the File class describes the class as:

An abstract representation of file and directory pathnames.

File is only a representation of a pathname, with a few methods concerning the filesystem (like exists()) and directory handling but actual streaming input and output is done elsewhere. Streams can be opened and closed, files cannot.

(My personal opinion is that it's rather unfortunate that Sun then went on to create RandomAccessFile, causing much confusion with its inconsistent naming.)



回答2:

java.io.File doesn't represent an open file, it represents a path in the filesystem. Therefore having close method on it doesn't make sense.

Actually, this class was misnamed by the library authors, it should be called something like Path.



回答3:

Essentially random access file wraps input and output streams in order to manage the random access. You don't open and close a file, you open and close streams to a file.



回答4:

A BufferedReader can be opened and closed but a File is never opened, it just represents a path in the filesystem.



回答5:

Say suppose, you have File f = new File("SomeFile"); f.length(); You need not close the Files, because its jsut the representation of path. You should always consider to close only reader/writers and infact streams.



标签: java file-io