From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] Literate Programming (was Comments in early Unix systems)
Date: Thu, 22 Mar 2018 13:07:36 -0400 [thread overview]
Message-ID: <c6878787-23b3-3c37-7133-d106d332d3e1@telegraphics.com.au> (raw)
In-Reply-To: <201803221630.w2MGU5Aw016397@freefriends.org>
On 2018-03-22 12:30 PM, arnold at skeeve.com wrote:
> Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>
>> Knuth offered the remedy of "literate programming", which
>> might help in academic circles. In business, probably not.
>
> IMHO this is too bad. Code I've written using LP is generally
> more correct earlier on than otherwise. And it's very enjoyable
> to write code and explanation at the same time; I feel like I'm
> talking out loud directly to my reader, a person, and not just
> coding for myself or the compiler.
>
> Significant proofs by example are Knuth's TeX and MetaFont,
> and the lcc compiler by Dave Hanson and <I forgot>.
Chris Fraser (AT&T Bell Labs at the time).
As you say, the whole book is a literate program:
https://www.pearson.com/us/higher-education/program/Hanson-Retargetable-C-Compiler-A-Design-and-Implementation/PGM166351.html
>
> Shameless plug: I have written a small LP system in gawk designed
> for use with the Texinfo markup language. ...
> Thanks,
>
> Arnold
>
prev parent reply other threads:[~2018-03-22 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 13:49 [TUHS] Comments in early Unix systems Doug McIlroy
2018-03-22 14:29 ` Nemo
2018-03-22 16:30 ` [TUHS] Literate Programming (was Comments in early Unix systems) arnold
2018-03-22 16:48 ` Jon Steinhart
2018-03-22 17:07 ` Toby Thain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c6878787-23b3-3c37-7133-d106d332d3e1@telegraphics.com.au \
--to=toby@telegraphics.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).