• This organization of the package follows the rule

• pipes-text : pipes-bytestring :: text : bytestring

Familiarity with the other three packages should give one an idea what to expect where. The package has three principal modules, Pipes.Text , Pipes.Text.Encoding and Pipes.Text.IO; the division has more or less the significance it has in the text library. A fourth module Pipes.Prelude.Text is explained below.

Note that the module Pipes.Text.IO is present as a convenience (as is Data.Text.IO). Official pipes IO would use Pipes.ByteString together with the bytestring decoding functions in Pipes.Text.Encoding. In particular, the Pipes.Text.IO functions use Text exceptions.

The fourth module Pipes.Prelude.Text exports line-based Text producers and consumers as a drop-in replacement for the String material in Pipes.Prelude and Pipes.Safe.Prelude. They can be used as one uses Pipes.Prelude without reference to the rest of this package. See the caveats in the documentation for that module.

Pipes.Text.IO and Pipes.Prelude.Text use version 0.11.3 or later of the text library. To use a (very) old version of text, install with the flag -fnoio

---

[Skip to Readme]

Modules

[Index]

Flags

Automatic Flags

Name	Description	Default
noio	Use a version of text earlier than 0.11.3	Disabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

• pipes-text-0.0.2.0.tar.gz [browse] (Cabal source package)
• Package description (as included in the package)

Maintainer's Corner

Package maintainers

• PeterJones, MichaelThompson

For package maintainers and hackage trustees

• edit package information

Candidates

• 0.0.0.0, 0.0.0.5, 0.0.0.7, 0.0.0.8, 0.0.0.9, 0.0.0.10, 0.0.0.11, 0.0.0.12, 0.0.0.16, 0.0.1.0, 0.1.0.0, 1.0.0, 1.0.1