Pipeline programming: Difference between revisions

Content deleted Content added
Related page added in See also section, May be that page can be merged as well
 
(One intermediate revision by one other user not shown)
Line 1:
*#redirect [[Pipeline (software)]]
{{Unreferenced|auto=yes|date=December 2009}}
{{Original research|date=May 2010}}
{{Programming paradigms}}
{{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==
*[[Windows PowerShell]]
*[[Hartmann pipeline]]
*[[Bash (Unix shell)|Bash]]
 
==See also==
* [[Pipeline (software)]]
* [[Hartmann pipeline]]
* [[Function composition (computer science)]]
* [[Architecture description language]]
* [[Scripting language]]
* [[Art pipeline|Art Pipeline]]
 
{{Programming language}}
 
{{DEFAULTSORT:Pipeline Programming}}
[[Category:Programming paradigms]]
[[Category:Inter-process communication]]
 
 
{{Prog-lang-stub}}