The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] TeX and groff (was: roff(7))
Date: Thu, 13 Jan 2022 05:27:32 +1100	[thread overview]
Message-ID: <20220112182731.xoz4fugdbpxv5lbm@localhost.localdomain> (raw)
In-Reply-To: <202201121753.20CHrSDp2410765@darkstar.fourwinds.com>

[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]

At 2022-01-12T09:53:28-0800, Jon Steinhart wrote:
> Ralph Corderoy writes:
> > > I never understood "interpolating a register" to have any relation
> > > to the definition of interpolate that I learned in math.
> >
> > The first definition makes sense of it:
> >
> >     1. (transitive, intransitive) To introduce (something) between
> >     other things; especially to insert (possibly spurious) words
> >     into a text.
> >
> >         in verse 74, the second line is clearly interpolated
[...]
> Yeah, I looked it up too.  Yes, the argument can be made that one of
> the definitions can be forced to sort of fit; I'm guessing that #3
> didn't exist when troff was written.  So I'm gonna stick to my point
> that using that word is awkward and makes the document a bit harder to
> understand.  Especially in the context of programming languages, of
> which troff is one.  To the best of my knowledge, nobody talks about
> "a = b;" as interpolating b.

I've found the term highly useful and have greatly increased its usage
in groff documentation.  (I have been a stickler for a disciplined
lexicon in every software project I've been involved in.)

I prefer it to a popular alternative, "expansion", which is
misleading--especially to novices, who then make the reasonable
assumption, given the everyday meaning of that word, that whatever
results from the process will be larger in some sense than what was
there before.

An argument could be made for the word "replacement", but I've found it
useful to reserve that plain-spoken term for discussion of things a
human might do (perhaps in the course of editing a document or
developing a macro).  To my ear, "interpolation" sounds fancy enough to
refer to something you let a machine do, without being _excessively_
technical in tone.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-12 18:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  2:49 Jon Steinhart
2022-01-12 10:38 ` Ralph Corderoy
2022-01-12 17:53   ` Jon Steinhart
2022-01-12 18:27     ` G. Branden Robinson [this message]
2022-01-12 19:02       ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2022-01-13 17:31 Douglas McIlroy
2022-01-11 13:37 Nelson H. F. Beebe
2022-01-10 21:12 Bakul Shah
2022-01-10 21:06 Jon Steinhart
2022-01-11 11:06 ` Ralph Corderoy
2022-01-11 14:52   ` John Cowan
2021-12-31 15:47 [TUHS] roff(7) Douglas McIlroy
2021-12-31 23:07 ` George Michaelson
2021-12-31 23:40   ` Larry McVoy
2022-01-01  0:56     ` [TUHS] TeX and groff (was: roff(7)) Greg 'groggy' Lehey
2022-01-01  3:15       ` Larry McVoy
2022-01-10 19:00         ` Blake McBride
2022-01-10 20:21           ` Jon Forrest
2022-01-11 22:48             ` Blake McBride
2022-01-11 23:18               ` Larry McVoy
2022-01-12  1:19                 ` Dave Horsfall
2022-01-12  1:46                 ` Blake McBride
2022-01-12  2:12                 ` Bakul Shah
2022-01-12 15:49                   ` Larry McVoy
2022-01-12 16:22                     ` Adam Thornton
2022-01-12  0:06               ` Jon Steinhart
2022-01-12  1:48                 ` Blake McBride
2022-01-12  0:29               ` Nemo Nusquam
2022-01-12  1:53                 ` Blake McBride
     [not found]               ` <E3CC4B8A-4E88-4339-A4D3-4ED26BA80620@gmail.com>
2022-01-12  0:44                 ` Jon Forrest
2022-01-12  2:00                   ` Blake McBride
2022-01-12  2:10                     ` David Arnold
2022-01-12  2:26                       ` Adam Thornton
2022-01-12 19:54                     ` John Cowan
2022-01-13 10:13                       ` Thomas Paulsen
2022-01-13 20:00                         ` John Cowan
2022-01-10 20:33           ` Larry McVoy
2022-01-10 20:37             ` Richard Salz
2022-01-10 21:04               ` Dan Cross
2022-01-10 21:48                 ` Nemo Nusquam
2022-01-11  2:25                 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11  2:47                   ` Larry McVoy
2022-01-12  1:19             ` Mary Ann Horton
2022-01-12  2:03               ` Blake McBride
2022-01-12  2:10               ` Bakul Shah
2022-01-12  3:44                 ` Dan Cross
2022-01-12 16:48               ` Steffen Nurpmeso
2022-01-10 20:46           ` Steffen Nurpmeso

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=20220112182731.xoz4fugdbpxv5lbm@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=tuhs@minnie.tuhs.org \
    --subject='Re: [TUHS] TeX and groff (was: roff(7))' \
    /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

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).