FilePath -package:filepath

File and directory names are values of type String, whose precise meaning is operating system dependent. Files can be opened, yielding a handle which can then be used to operate on the contents of that file.
Internal stuff: support for ByteString FilePaths
Internal stuff: support for ByteString FilePaths
A module for FilePath operations exposing System.FilePath plus some additional operations. Windows note: The extension methods (<.>, takeExtension etc) use the Posix variants since on Windows "//*" <.> "txt" produces "//*\\.txt" (which is bad for FilePattern values).
FilePath is a collection of FileName TODO: Eq and Ord are implemented using Show This is not very efficient and would need to be improved Also, it is possible the ordering is not necessary what we want in this case. A FilePath is one of the following:
  • An Absolute:
  • starts with one of the follwing "/"
  • A relative:
  • don't start with a "/"
  • authorised:
  • "/"
  • "filepath"
  • "."
  • ".."
  • "workhaskellhs-foundation"
  • unauthorised
  • "path//"
# Opaque implementation for FilePath The underlying type of a FilePath is a ByteArray. It is indeed like this because for some systems (Unix systems) a FilePath is a null terminated array of bytes. # FilePath and FileName for type checking validation In order to add some constraint at compile time, it is not possible to append (</>) a FilePath to another FilePath. You can only append (</>) a FileName to a given FilePath.
Deprecated: Use Path.File instead.
The equivalent of System.FilePath on raw (byte string) file paths. Not all functions of System.FilePath are implemented yet. Feel free to contribute!
Hole containing a filepath for a data file
Utilities for dealing with YAML config files which contain relative file paths.
Return the name of the file being visited.
Extract the AbsolutePath to be used as FilePath.
Gets the local pathname for File, if one exists. This call does no blocking i/o.
Deprecated: Use Path.file instead.
File path.