Literate programming is the practice of weaving code into a document such that paragraphs, equations, and diagrams can explain the code, and the code can produce numbers, figures, and tables (and diagrams and even equations and paragraphs).
The R project has a task view devoted to reproducible research listing many of the different approaches to literate programming for R.
Initiatives like the literate programming
 tries to couple the creation of computer source code and the associated documentation, stating that the programmer main task is to explain his code to other programmers, not only to computers.
Four programs have appeared since July, 1987, when this column was comissioned to explore different approaches to literate programming
supports the idea that we should not try to instruct the computer what to do, but rather we should try to tell humans what we want the computer to do .
SPIDER should make one literate programming
tool, WEB, available to a much larger audience.
Overview So far, all reviews of literate programs in Communications have criticized the content rather than the use of literate programming
In reply to last year's "Programming Pearls" about literate programming
, Richard Botting wrote to suggest that very different solutions would be proferred by a programmer trained in Michael Jackson's method of program design.
Index to Communications of the ACM Volume 30, 1987 BIBLIOGRAPHY AUTHOR INDEX ARTICLE INDEX REPORT INDEX COMPUTING PRACTICES INDEX RESEARCH CONTRIBUTION INDEX EDITORIALS, VIEWPOINTS, PRESIDENTS LETTERS, FROM WASHINGTON INDEX PROGRAMMING PEARLS INDEX LITERATE PROGRAMMING
INDEX ACM FORUM INDEX TECHNICAL CORRESPONDENCE INDEX OBITUARY
In May and June 1986, Programming Pearls took up literate programming
, an approach to programming espoused by Donald Knuth.
Several readers wondered how well a small example can serve to illustrate the features of system for literate programming