features:pipes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
features:pipes [2015/12/29 20:20] – admin | features:pipes [2015/12/29 20:33] – [Dating the Creation of Pipes] admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Pipes ====== | ====== Pipes ====== | ||
- | The idea of connecting an output from one process, via an in-kernel memory buffer, to the input of another process is entirely original to Unix. | + | **Wikipedia: |
- | Doug McIlroy, in 1964, had proposed that "We should have some ways of connecting programs like garden hose–screw in another | + | The idea of connecting an output from one process, via an in-kernel memory buffer, to the input of another |
+ | Doug McIlroy, in 1964, had proposed that "We should have some ways of connecting programs like garden hose – screw in another segment when it becomes necessary to massage data in another way. This is the way of IO also." (Dennis Ritchie, [[https:// | ||
===== The Evolution of Pipes ===== | ===== The Evolution of Pipes ===== | ||
Line 18: | Line 19: | ||
To make a pipeline, command operators could be stacked up. Thus, to sort //input,// paginate it neatly, and print the result off-line, one would write | To make a pipeline, command operators could be stacked up. Thus, to sort //input,// paginate it neatly, and print the result off-line, one would write | ||
- | + | < | |
- | < | + | input sort paginate offprint |
</ | </ | ||
In today' | In today' | ||
- | < | + | < |
+ | sort input | pr | opr | ||
</ | </ | ||
Line 63: | Line 65: | ||
According to the [[: | According to the [[: | ||
+ | |||
+ | The Second Edition of Unix, dated June 1972, didn't have pipes; by January 15, 1973, Unix did have pipes. Doug McIlroy put out the notice for a [[http:// | ||
features/pipes.txt · Last modified: 2022/09/16 18:47 by 123.219.209.121