IN stage v1.1

Pipelines v1.9

Purpose, Operands, Streams used, Usage notes, Examples, See also

Home

Syntax

>>__IN_________________________________________________________________________________><

Purpose

Use the IN stage to read records from the STDIN stream, if it is connected, or from the CALLPIPE stage of the calling pipeline. IN splits its input at Line-Feed characters; discarding both individual and groups of Carriage-Return characters and writes the resulting records to its primary output stream.

Operands

None.

Streams used

The following streams are used by the IN stage:

Stream	Action
Input streams	IN reads records from the STDIN stream, if it is connected, or from the CALLPIPE stage of the calling pipeline.
Primary output stream	IN writes records to its primary output stream.

Usage notes

1)	IN does not delay the records.
2)	When IN reads from its STDIN stream, it reads its input records one at a time; waiting for each one to be consumed from its primary output stream before reading another. When IN reaches end-of-file on its STDIN stream, IN disconnects its primary output stream and the stage ends.
3)	IN splits its input at Line-Feed characters; discarding both individual and groups of Carriage-Return characters and writes the resulting records to its primary output stream. IN discards the last Line-Feed character of its input where this would produce a null output record.
4)	You should only specify the IN stage command once in a pipeline; otherwise the results will be unpredictable.
5)	IN verifies that its secondary input and secondary output streams are not connected and then begins execution.

Examples

The following pipeline shows the path environment variable parsed into its individual values.

D:\>path | pipe “in | split at str /;/ | specs ws /=/ w-1 1 | cons”
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\Program files\TenFiftyTwo\Pipelines

See also

 
Reference the following links for additional information:
 
CALLPIPE, CONSOLE, OUT