|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Pipelines
November/December 2003 (vol. 20 no. 6)
pp. 17-19
| ASCII Text | x | ||
| Dave Thomas, Andy Hunt, "Pipelines," IEEE Software, vol. 20, no. 6, pp. 17-19, November/December, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2003.1241360, author = {Dave Thomas and Andy Hunt}, title = {Pipelines}, journal ={IEEE Software}, volume = {20}, number = {6}, issn = {0740-7459}, year = {2003}, pages = {17-19}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1241360}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Pipelines IS - 6 SN - 0740-7459 SP17 EP19 EPD - 17-19 A1 - Dave Thomas, A1 - Andy Hunt, PY - 2003 VL - 20 JA - IEEE Software ER - | |||
One of the underlying philosophies of the Unix command shell is the idea of the pipeline: Take a set of small, specialized programs and let them interact by feeding the output of one into the input of the next. By stringing simple programs together in this way, rich behavior can emerge. Pipelines can let you replace complex program logic with a chain of far simpler discrete steps.
Citation:
Dave Thomas, Andy Hunt, "Pipelines," IEEE Software, vol. 20, no. 6, pp. 17-19, Nov.-Dec. 2003, doi:10.1109/MS.2003.1241360
Usage of this product signifies your acceptance of the Terms of Use.