From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] [Haskell-cafe] Terminator syntax style (Was: Nested (=>) (Was: On finding the right exposition...))
Date: Thu, 7 Oct 2021 09:50:42 -0400 [thread overview]
Message-ID: <CAKH6PiVCCo2P09cto4x4iCuw3oA+XYyGtKvrMiyV+XeG1xL_hA@mail.gmail.com> (raw)
Apropos of "finding the right exposition"!, consider the cited wiki article:
Separator: There is a symbol between each element.
The more carefully you read this the more it becomes nonsense.
1, "Each element" is an individual. You can't put something between an
individual.
2 The defining sentence states a property of a representation of a
sequence. It fails to indicate that "separator" is the symbol's role.
In fact what's being defined is "separator notation", not the bare
word "separator". This usage appears only later in the article. It
should be employed throughout--most importantly in the title and the
definition. The same goes for "terminator".
Doug
next reply other threads:[~2021-10-07 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 13:50 Douglas McIlroy [this message]
2021-10-07 13:54 ` William Cheswick
2021-10-07 19:28 ` John Cowan
2021-10-07 19:52 Norman Wilson
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=CAKH6PiVCCo2P09cto4x4iCuw3oA+XYyGtKvrMiyV+XeG1xL_hA@mail.gmail.com \
--to=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@minnie.tuhs.org \
/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).