A component that performs a computation with no inputs nor outputs is a PerformerComponent.

A component that consumes values from a Source is called ConsumerComponent.

A component that produces values and puts them into a Sink is called ProducerComponent.

The TransducerComponent type represents computations that transform a data stream.

The SplitterComponent type represents computations that distribute data acording to some criteria. A splitter should distribute only the original input data, and feed it into the sinks in the same order it has been read from the source. If the two 'Sink c x' arguments of a splitter are the same, the splitter must act as an identity transform.

The constant cost of each I/O-performing component.

A TransducerComponent that converts a stream of one type to another.

Adjusts the argument consumer to consume the stream of a data type coercible to the type it was meant to consume.

Adjusts the argument producer to produce the stream of a data type coercible from the type it was meant to produce.

Adjusts the argument splitter to split the stream of a data type isomorphic to the type it was meant to split.

ProducerComponent fromStdIn feeds the given sink from the standard input.

ProducerComponent fromFile opens the named file and feeds the given sink from its contents.

ProducerComponent fromHandle feeds the given sink from the open file handle.

ConsumerComponent toStdOut copies the given source into the standard output.

ConsumerComponent toFile opens the named file and copies the given source into it.

ConsumerComponent appendFile opens the name file and appends the given source to it.

ConsumerComponent toHandle copies the given source into the open file handle.

produceFrom produces the contents of the given argument.

ConsumerComponent consumeInto collects the given source into the return value.

The suppress consumer suppresses all input it receives. It is equivalent to substitute []

The erroneous consumer reports an error if any input reaches it.

TransducerComponent id passes its input through unmodified.

TransducerComponent unparse removes all markup from its input and passes the content through.

TransducerComponent parse prepares input content for subsequent parsing.

The lowercase transforms all uppercase letters in the input to lowercase, leaving the rest unchanged.

The uppercase transforms all lowercase letters in the input to uppercase, leaving the rest unchanged.

The count transducer counts all its input values and outputs the final tally.

Converts each input value x to show x.

Performs the same task as the substring splitter, but instead of splitting it outputs the input as Markup x OccurenceTag in order to distinguish overlapping strings.

TransducerComponent group collects all its input into a single list item.

TransducerComponent concatenate flattens the input stream of lists of values into the output stream of values.

Same as concatenate except it inserts the given separator list between every two input lists.

SplitterComponent everything feeds its entire input into its true sink.

SplitterComponent nothing feeds its entire input into its false sink.

SplitterComponent marked passes all marked-up input sections to its true sink, and all unmarked input to its false sink.

SplitterComponent markedContent passes the content of all marked-up input sections to its true sink, while the outermost tags and all unmarked input go to its false sink.

SplitterComponent markedWith passes input sections marked-up with the appropriate tag to its true sink, and the rest of the input to its false sink. The argument select determines if the tag is appropriate.

SplitterComponent contentMarkedWith passes the content of input sections marked-up with the appropriate tag to its true sink, and the rest of the input to its false sink. The argument select determines if the tag is appropriate.

SplitterComponent one feeds all input values to its true sink, treating every value as a separate section.

SplitterComponent substring feeds to its true sink all input parts that match the contents of the given list argument. If two overlapping parts of the input both match the argument, both are sent to true and each is preceded by an empty chunk on false.

SplitterComponent whitespace feeds all white-space characters into its true sink, all others into false.

SplitterComponent letters feeds all alphabetical characters into its true sink, all other characters into | false.

SplitterComponent digits feeds all digits into its true sink, all other characters into false.

SplitterComponent nonEmptyLine feeds line-ends into its false sink, and all other characters into true.

The sectioning splitter line feeds line-ends into its false sink, and line contents into true. A single line-end can be formed by any of the character sequences "\n", "\r", "\r\n", or "\n\r".

Converts a ConsumerComponent into a TransducerComponent with no output.

Class PipeableComponentPair applies to any two components that can be combined into a third component with the following properties:

• The input of the result, if any, becomes the input of the first component.

  • The output produced by the first child component is consumed by the second child component.
  • The result output, if any, is the output of the second component.

Class JoinableComponentPair applies to any two components that can be combined into a third component with the following properties:

• if both argument components consume input, the input of the combined component gets distributed to both components in parallel,

  • if both argument components produce output, the output of the combined component is a concatenation of the complete output from the first component followed by the complete output of the second component, and

The join combinator may apply the components in any order.

The sequence combinator makes sure its first argument has completed before using the second one.

Combinator prepend converts the given producer to transducer that passes all its input through unmodified, except | for prepending the output of the argument producer to it. | prepend prefix = join (substitute prefix) asis

Combinator append converts the given producer to transducer that passes all its input through unmodified, finally | appending to it the output of the argument producer. | append suffix = join asis (substitute suffix)

The substitute combinator converts its argument producer to a transducer that produces the same output, while | consuming its entire input and ignoring it.

The snot (streaming not) combinator simply reverses the outputs of the argument splitter. In other words, data that the argument splitter sends to its true sink goes to the false sink of the result, and vice versa.

The >& combinator sends the true sink output of its left operand to the input of its right operand for further splitting. Both operands' false sinks are connected to the false sink of the combined splitter, but any input value to reach the true sink of the combined component data must be deemed true by both splitters.

A >| combinator's input value can reach its false sink only by going through both argument splitters' false sinks.

Combinator && is a pairwise logical conjunction of two splitters run in parallel on the same input.

Combinator || is a pairwise logical disjunction of two splitters run in parallel on the same input.

The recursive combinator while feeds the true sink of the argument splitter back to itself, modified by the argument transducer. Data fed to the splitter's false sink is passed on unmodified.

The recursive combinator nestedIn combines two splitters into a mutually recursive loop acting as a single splitter. The true sink of one of the argument splitters and false sink of the other become the true and false sinks of the loop. The other two sinks are bound to the other splitter's source. The use of nestedIn makes sense only on hierarchically structured streams. If we gave it some input containing a flat sequence of values, and assuming both component splitters are deterministic and stateless, an input value would either not loop at all or it would loop forever.

The foreach combinator is similar to the combinator ifs in that it combines a splitter and two transducers into another transducer. However, in this case the transducers are re-instantiated for each consecutive portion of the input as the splitter chunks it up. Each contiguous portion of the input that the splitter sends to one of its two sinks gets transducered through the appropriate argument transducer as that transducer's whole input. As soon as the contiguous portion is finished, the transducer gets terminated.

The having combinator combines two pure splitters into a pure splitter. One splitter is used to chunk the input into contiguous portions. Its false sink is routed directly to the false sink of the combined splitter. The second splitter is instantiated and run on each portion of the input that goes to first splitter's true sink. If the second splitter sends any output at all to its true sink, the whole input portion is passed on to the true sink of the combined splitter, otherwise it goes to its false sink.

The havingOnly combinator is analogous to the having combinator, but it succeeds and passes each chunk of the input to its true sink only if the second splitter sends no part of it to its false sink.

Combinator followedBy treats its argument SplitterComponents as patterns components and returns a SplitterComponent that matches their concatenation. A section of input is considered true by the result iff its prefix is considered true by argument s1 and the rest of the section is considered true by s2. The splitter s2 is started anew after every section split to true sink by s1.

The even combinator takes every input section that its argument splitter deems true, and feeds even ones into its true sink. The odd sections and parts of input that are false according to its argument splitter are fed to even splitter's false sink.

The result of combinator first behaves the same as the argument splitter up to and including the first portion of the input which goes into the argument's true sink. All input following the first true portion goes into the false sink.

The result of combinator uptoFirst takes all input up to and including the first portion of the input which goes into the argument's true sink and feeds it to the result splitter's true sink. All the rest of the input goes into the false sink. The only difference between first and uptoFirst combinators is in where they direct the false portion of the input preceding the first true part.

The prefix combinator feeds its true sink only the prefix of the input that its argument feeds to its true sink. All the rest of the input is dumped into the false sink of the result.

The result of the combinator last is a splitter which directs all input to its false sink, up to the last portion of the input which goes to its argument's true sink. That portion of the input is the only one that goes to the resulting component's true sink. The splitter returned by the combinator last has to buffer the previous two portions of its input, because it cannot know if a true portion of the input is the last one until it sees the end of the input or another portion succeeding the previous one.

The result of the combinator lastAndAfter is a splitter which directs all input to its false sink, up to the last portion of the input which goes to its argument's true sink. That portion and the remainder of the input is fed to the resulting component's true sink. The difference between last and lastAndAfter combinators is where they feed the false portion of the input, if any, remaining after the last true part.

The suffix combinator feeds its true sink only the suffix of the input that its argument feeds to its true sink. All the rest of the input is dumped into the false sink of the result.

SplitterComponent startOf issues an empty true section at the beginning of every section considered true by its argument splitter, otherwise the entire input goes into its false sink.

SplitterComponent endOf issues an empty true section at the end of every section considered true by its argument splitter, otherwise the entire input goes into its false sink.

Combinator ... tracks the running balance of difference between the number of preceding starts of sections considered true according to its first argument and the ones according to its second argument. The combinator passes to true all input values for which the difference balance is positive. This combinator is typically used with startOf and endOf in order to count entire input sections and ignore their lengths.

Converts a splitter into a parser.

This splitter splits XML markup from data content. It is used by parseXMLTokens.

The XML token parser. This parser converts plain text to parsed text, which is a precondition for using the remaining XML components.

Splits all top-level elements with all their content to true, all other input to false.

Splits the content of all top-level elements to true, their tags and intervening input to false.

Similiar to (having element), except it runs the argument splitter only on each element's start tag, not on the entire element with its content.

Splits every attribute specification to true, everything else to false.

Splits every element name, including the names of nested elements and names in end tags, to true, all the rest of input to false.

Splits every attribute name to true, all the rest of input to false.

Splits every attribute value, excluding the quote delimiters, to true, all the rest of input to false.

A Component carries a value and metadata about the value. It can be configured to use a specific number of threads.

Show details of the given component's configuration.

Function atomic takes the component name and its cost creates a single-threaded component with no subcomponents.

Applies a unary combinator to the component payload. The resulting component has the original one as its subComponents, and its cost is the sum of the original component's cost and the combinator cost.

Combines two components into one, applying combinator to their contents. The combinator takes a flag denoting if its arguments should run in parallel. The cost and usingThreads of the result assume the parallel execution of the argument components.

Combines two components into one, applying combinator to their contents. The cost and usingThreads of the result assume the sequential execution of the argument components.

Combines three components into one. The first component runs in parallel with the latter two, which are considered alternative to each other.

Builds a tree of recursive components. The combinator takes a list of pairs of a boolean flag denoting whether the level should be run in parallel and the value.

Converts an XML entity name into the text value it represents: expandXMLEntity "lt" = "<".