Pipeline programming: Difference between revisions

Revision as of 17:18, 16 August 2010

Revision as of 19:21, 13 January 2012

Line 4:

{{Merge to|Pipeline (software)|date=August 2010}}

When a [[programming language]] is originally designed without any syntax to nest function calls, '''pipeline programming''' is a simple syntax change to add it. The programmer connects notional program modules into a flow structure, by analogy to a physical pipeline carrying reaction products through a [[chemical plant|chemical]] or other plant. The best-known example is the [[pipeline (Unix)|UNIXUnix pipe system]], but many high level software design tools (such as the [[openDX]] display suite) provide a [[GUI]] pipeline programming tool that helps visualize data flow through thea program. A [[Datadata Flowflow Diagramdiagram]] (DFD) maps well to pipeline programming. Note thatHowever, exception handling can be one of the weak pointsweaknesses.{{Clarify|date=May 2010}}.

==Examples==

*[[Windows PowerShell]]

*[[Hartmann pipeline]]

*[[Bash (Unix shell)|Bash]]

==See also==

* [[Pipeline (software)]]

* [[Hartmann pipeline]]

* [[Function composition (computer science)|Function composition]]

* [[Architecture description language]]

* [[Scripting language]]

Line 25:

{{CompuProg-lang-stub}}