This class and its children serve to unify handling of files and directories.
This class and its children serve to unify handling of files and directories. These files and directories may or may not have some real counter part within the file system. For example, some file handles reference files within a zip archive or virtual ones that exist only in memory.
Every abstract file has a path (i.e. a full name) and a name (i.e. a short name) and may be backed by some real File. There are two different kinds of abstract files: regular files and directories. Regular files may be read and have a last modification time. Directories may list their content and look for subfiles with a specified name or path and of a specified kind.
The interface does not allow to access the content.
The class symtab.classfile.AbstractFileReader
accesses
bytes, knowing that the character set of classfiles is UTF-8. For
all other cases, the class SourceFile
is used, which honors
global.settings.encoding.value
.
Note: This library is considered experimental and should not be used unless you know what you are doing.
An abstraction for directories.
An abstraction for directories.
2.8 Note: This is library is considered experimental and should not be used unless you know what you are doing.
An abstraction for files.
An abstraction for files. For character data, a Codec can be supplied at either creation time or when a method involving character data is called (with the latter taking precedence if supplied.) If neither is available, the value of scala.io.Codec.default is used.
2.8 Note: This is library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
The Path constructor is private so we can enforce some semantics regarding how a Path might relate to the world.
The Path constructor is private so we can enforce some semantics regarding how a Path might relate to the world.
Note: This library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
This class implements an abstract file backed by a File.
This class implements an abstract file backed by a File.
Note: This library is considered experimental and should not be used unless you know what you are doing.
abstract base class of a source file used in the compiler
Note: This library is considered experimental and should not be used unless you know what you are doing.
An in-memory directory.
This class implements an in-memory file.
This class implements an in-memory file.
1.0, 23/03/2004 Note: This library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
Note: This library is considered experimental and should not be used unless you know what you are doing.
A distinguished object so you can avoid both null and Option.
A distinguished object so you can avoid both null and Option.
Note: This library is considered experimental and should not be used unless you know what you are doing.
An object representing a missing source file.
An abstraction for filesystem paths.
An abstraction for filesystem paths. The differences between Path, File, and Directory are primarily to communicate intent. Since the filesystem can change at any time, there is no way to reliably associate Files only with files and so on. Any Path can be converted to a File or Directory (and thus gain access to the additional entity specific methods) by calling toFile or toDirectory, which has no effect on the filesystem.
Also available are createFile and createDirectory, which attempt to create the path in question.
2.8 Note: This library is considered experimental and should not be used unless you know what you are doing.
Traits for objects which can be represented as Streams.
Traits for objects which can be represented as Streams.
2.8 Note: This library is considered experimental and should not be used unless you know what you are doing.
An abstraction for zip files and streams.
An abstraction for zip files and streams. Everything is written the way it is for performance: we come through here a lot on every run. Be careful about changing it.
2.0, Note: This library is considered experimental and should not be used unless you know what you are doing.