Leggi l’articolo in italiano
Sticker 003 · Outstanding Programmers Album. Open Douglas McIlroy’s sticker · Browse the album.
Douglas McIlroy is a central figure in the Unix software-tools tradition, best known for promoting pipes: connections that let one program’s output become another program’s input. His story shows that an outstanding contribution can be about helping simple tools cooperate, as well as inventing a new tool.
After Ken Thompson and Dennis Ritchie, we meet someone less familiar to the wider public. His place in the album concerns technical work, design and care for quality—not a popularity ranking.
Photo: Denise Panyik-Dale, CC BY 2.0, via Wikimedia Commons. The file is an existing Commons crop; no additional editorial crop has been applied.
Who is Douglas McIlroy, and what was his role in Unix?
A programmer trained in physics and mathematics, McIlroy headed the Bell Labs research department in which Unix was born. His Dartmouth personal page describes work spanning languages, compilers, stream processing, algorithms and documentation.
A Cornell profile published on March 15, 2024 highlights the relationship between his macro research and connecting software tools. To understand the contribution, start with a familiar problem: data needs sorting, filtering and summarising, but no single program does exactly everything.
Unix pipes, explained without jargon
Imagine three people around a table. One prepares a list of words, another sorts it, and the third counts how often each word occurs. No one needs to do the entire job; they only need to pass the list in a format the next person understands.
A pipeline follows a similar idea. In shell commands, | normally connects the standard output of the command on its left to the standard input of the command on its right. The connection carries data; it does not interpret the meaning or repair incompatible formats.
Simplicity does not remove design: it also places design in the interfaces. If one stage produces something the next can read, a link may be replaced without rewriting everything. This is an educational analogy, not a literal description of people working inside a computer.
McIlroy proposed pipes; Thompson implemented them in Unix
In his August 18, 1989 interview with Michael S. Mahoney, McIlroy recalled repeatedly advocating connections between processes. Ken Thompson implemented pipes in Unix and adapted tools to standard streams. Distinguishing those roles avoids assigning the whole implementation to one person.
The album therefore recognises design and cultural contributions alongside others’ work. An idea gains strength when it becomes usable; an implementation becomes more useful when compatible tools are available. Each supports the other.
A small pipeline to try: an original teaching example
This line was prepared for this article. It is not historical McIlroy code. In a shell with printf, sort and uniq, it produces occurrence counts:
printf '%s\n' pear apple pear | sort | uniq -c
Ignoring alignment spaces, the result is 1 apple and 2 pear. printf emits one word per line, sort groups equal words, and uniq -c counts consecutive repetitions. Sorting matters: otherwise equal words separated by others could be counted in different groups.
This example does not credit McIlroy with the current versions of these commands. It demonstrates composition using available tools—an essential distinction between an idea’s legacy and authorship of a source file.
Authentic code: Antiquicksort and difficult test cases
The author’s source-code index links to aqsort.c, Antiquicksort. The file carries M. Douglas McIlroy’s 1998 copyright and explicit permission to use or copy with the notice attached. Below are that notice and a short continuous excerpt from the body of aqsort:
/* Copyright 1998, M. Douglas McIlroy
Permission is granted to use or copy with this notice attached. */
qsort(ptr, n, sizeof(*ptr), cmp);
for(i=1;i<n;i++)
assert(val[ptr[i]]==val[ptr[i-1]]+1);
free(ptr);
return ncmp;
This is an excerpt, not a standalone program: declarations, the comparator and the rest of the function are omitted. It is not AI-reconstructed historical code. The retained notice states the file’s specific permission; we do not relabel it as MIT or GPL.
Here qsort invokes sorting; the loop with assert checks a property of the result constructed by the program. The code then releases memory and returns a comparison count. The project tests certain quicksort implementations with adversarial data under assumptions stated in the source; it does not prove that every sorting algorithm or every qsort is defective.
For a non-technical reader, the lesson is practical: software may appear fast with friendly examples and behave differently with difficult ones. Seeking an awkward case is part of quality, not a personal attack on the programmer.
Beyond pipes: algorithms, tools and manuals
McIlroy’s page lists contributions to tools including spell, diff, sort and join, and work to make Unix manuals concise and accurate. His source index also presents a sorting implementation associated with work with Jon Bentley: co-authorship must be preserved. Modern command versions have their own histories and maintainers.
Another educational legacy is a prime-number sieve: the MIT xv6 and Unix utilities lab credits McIlroy with the pipe-based design idea. We point to that learning path without attributing students’ programs to him.
Why he belongs in an album about free software’s foundations
McIlroy belongs to its technical roots and shared-tools culture. This does not automatically make every historical Unix version or every file on his website free software. His own source index distinguishes conditions for different works: availability on the Web and freedom to reuse are not synonyms.
An educational album should teach readers to consider ideas, authors and terms together. Pipelines can help people using free systems today, but historical credit does not replace checking the licence of the actual software being copied.
Three skills to bring to your own projects
Composition. Before building a huge program, ask whether smaller stages with clear responsibilities would help. They are not always the best choice, but the question is useful.
Checkability. Find an expected, testable result for each stage. In our small example, “pear” must occur twice, making verification immediate.
Precision. Name inputs, outputs and limitations clearly. A short but ambiguous manual does not help; concision matters when it preserves what readers need to understand.
Frequently asked questions about Douglas McIlroy
Did he invent Unix?
He was an important figure in the research group and tools culture; he should not replace Thompson and Ritchie in the story of Unix’s creation.
Is a pipe a program?
It is a communication mechanism. The shell provides notation for connecting programs through it.
Is the word-count pipeline his code?
No. It is this article’s original teaching example. The attributed historical excerpt, accompanied by its permission notice, comes from Antiquicksort.
Which sticker follows?
Number 004, Bill Joy. The album keeps numbered cards to help readers navigate contributions.
Nominate an outstanding programmer, well-known or otherwise
Who built a useful library, improved accessibility, maintained an essential project or created a tool others can study? Fame is not required: a concrete contribution and checkable sources are. This form also accepts corrections to the article.
Suggestions are reviewed before publication. Your name and email are optional and used for follow-up; contact details are not intended for publication. Do not include sensitive information.
Return to sticker 003 · Explore the complete album.
“One sticker, one story” series · 003 · November 19, 2026. Skills are educational readings of the work, not personality judgements.