Content deleted Content added
Jerryobject (talk | contribs) m Decapitalized: non-acronym (WP:ALLCAPS), non-proper nouns (WP:MOSCAPS). Clarify template moved after punctuation (WP:REFPUNC). Links: disambiguated (WP:D); removed needless pipe. Template updated (Template:Prog-lang-stub). |
m link exception handling using Find link |
||
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)|Unix 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 a program. A [[data flow diagram]] (DFD) maps well to pipeline programming. However, [[exception handling]] can be one of the weaknesses.{{Clarify|date=May 2010}}
==Examples==
| |||