Pipeline programming

From Wikipedia, the free encyclopedia

Programming paradigms

Agent-oriented Component-based Flow-based Pipeline Concatenative Concurrent computing Declarative (contrast: Imperative) Functional Dataflow Cell-oriented (spreadsheets) Reactive Goal-directed Constraint Constraint logic Logic Abductive logic Inductive logic Event-driven Feature-oriented Function-level (contrast: Value-level) Imperative (contrast: Declarative) Greater separation of concerns Aspect-oriented Subject-oriented Array (contrast: Scalar) Automata-based Object-oriented Class-based Prototype-based Procedural Structured Role-oriented Scalar (contrast: Array) Iterative (contrast: Recursive) Metaprogramming Attribute-oriented Automatic Generic Template Policy-based Language-oriented Grammar-oriented Dialecting Intentional Reflective Modular Nondeterministic Parallel computing Process-oriented Programming in the large and programming in the small Recursive (contrast: Iterative) Tree Value-level (contrast: Function-level) This box: view • talk • edit

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 or other plant. The best-known example is the 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 the program. A Data Flow Diagram (DFD) maps well to pipeline programming. Note that exception handling can be one of the weak points.

[edit] Examples

• Windows PowerShell
• Hartmann pipeline

[edit] See also

• Pipeline (software)
• Hartmann pipeline
• Function composition
• Architecture description language
• Scripting language