Dynamic effect for writing to a handle.

Since: 0.1

Lifted openBinaryFile.

Since: 0.1

Lifted withBinaryFile.

Since: 0.1

Lifted hClose.

Since: 0.1

Lifted hFlush.

Since: 0.1

Lifted hSetFileSize.

Since: 0.1

Lifted hSetBuffering.

Since: 0.1

Lifted hSeek.

Since: 0.1

Lifted hTell.

Since: 0.1

Lifted hSetEcho.

Since: 0.1

Lifted hPut.

Since: 0.1

Lifted hPutNonBlocking.

Since: 0.1

Runs HandleWriter in IO.

Since: 0.1

hPut and encodeUtf8.

Since: 0.1

hPutNonBlocking and encodeUtf8.

Since: 0.1

Write given error message to stderr and terminate with exitFailure.

Since: 0.1

Three kinds of buffering are supported: line-buffering, block-buffering or no-buffering. These modes have the following effects. For output, items are written out, or flushed, from the internal buffer according to the buffer mode:

• line-buffering: the entire output buffer is flushed whenever a newline is output, the buffer overflows, a hFlush is issued, or the handle is closed.
• block-buffering: the entire buffer is written out whenever it overflows, a hFlush is issued, or the handle is closed.
• no-buffering: output is written immediately, and never stored in the buffer.

An implementation is free to flush the buffer more frequently, but not less frequently, than specified above. The output buffer is emptied as soon as it has been written out.

Similarly, input occurs according to the buffer mode for the handle:

• line-buffering: when the buffer for the handle is not empty, the next item is obtained from the buffer; otherwise, when the buffer is empty, characters up to and including the next newline character are read into the buffer. No characters are available until the newline character is available or the buffer is full.
• block-buffering: when the buffer for the handle becomes empty, the next block of data is read into the buffer.
• no-buffering: the next input item is read and returned. The hLookAhead operation implies that even a no-buffered handle may require a one-character buffer.

The default buffering mode when a handle is opened is implementation-dependent and may depend on the file system object which is attached to that handle. For most implementations, physical files will normally be block-buffered and terminals will normally be line-buffered.

A space-efficient representation of a Word8 vector, supporting many efficient operations.

A ByteString contains 8-bit bytes, or by using the operations from Data.ByteString.Char8 it can be interpreted as containing 8-bit characters.

Haskell defines operations to read and write characters from and to files, represented by values of type Handle. Each value of this type is a handle: a record used by the Haskell run-time system to manage I/O with file system objects. A handle has at least the following properties:

• whether it manages input or output or both;
• whether it is open, closed or semi-closed;
• whether the object is seekable;
• whether buffering is disabled, or enabled on a line or block basis;
• a buffer (whose length may be zero).

Most handles will also have a current I/O position indicating where the next input or output operation will occur. A handle is readable if it manages only input or both input and output; likewise, it is writable if it manages only output or both input and output. A handle is open when first allocated. Once it is closed it can no longer be used for either input or output, though an implementation cannot re-use its storage while references remain to it. Handles are in the Show and Eq classes. The string produced by showing a handle is system dependent; it should include enough information to identify the handle for debugging. A handle is equal according to == only to itself; no attempt is made to compare the internal state of different handles for equality.

See openFile

Type representing filenames/pathnames.

This type doesn't add any guarantees over OsString.

A mode that determines the effect of hSeek hdl mode i.

A space efficient, packed, unboxed Unicode text type.