The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] Unix stories, Stephen Bourne and IF-FI in C code
Date: Mon, 9 Jan 2017 08:30:58 -0700	[thread overview]
Message-ID: <CAOkr1zU=s4uYL6m3AhRz7UcxaGRSrzgaAN5JPukHbw_UVAM_AQ@mail.gmail.com> (raw)
In-Reply-To: <934ec8dea21ce728b7c4e70a6ee2deb86af39d27@webmail.yaccman.com>

Just a quick note about Algol vs. Algol 68: The two are used
interchangeably (it seems) in this thread, but they're very different
languages, with very different control structures. Someone mentioned he had
studied Algol in school, which is plausible. If he in fact studied Algol
68, that's worth a story in its own right!

[Whoops... forgot to properly terminate that last sentence.]

fi

--Marc

On Sun, Jan 8, 2017 at 8:31 PM, Steve Johnson <scj at yaccman.com> wrote:

> I wasn't directly involved in this, but I do remember Dennis telling me
> essentially the same story.  I don't recall him mentioning Ken's name, just
> that "we couldn't use *od* because that was already taken".
>
> Steve B and I had adjacent offices, so I overheard a lot of the
> discussions about the Bourne shell.  The quoting mechanisms, in particular,
> got a lot of attention, I think to good end.  There was a lot more thought
> there than is evident from the surface...
>
> Steve (not Bourne)
>
>
> ----- Original Message -----
> From:
> "Norman Wilson" <norman at oclsc.org>
>
> To:
> <tuhs at tuhs.org>
> Cc:
>
> Sent:
> Sun, 08 Jan 2017 21:30:03 -0500
> Subject:
> Re: [TUHS] Unix stories, Stephen Bourne and IF-FI in C code
>
>
>
> Doug McIlroy:
>
> There was some pushback which resulted in the strange compromise
> of if-fi, case-esac, do-done. Alas, the details have slipped from
> memory. Help, scj?
>
> ====
>
> do-od would have required renaming the long-tenured od(1).
>
> I remember a tale--possibly chat in the UNIX Room at one point in
> the latter 1980s--that Steve tried and tried and tried to convince
> Ken to rename od, in the name of symmetry and elegance. Ken simply
> said no, as many times as it took. I don't remember who I heard this
> from; anyone still in touch with Ken who can ask him?
>
> Norman Wilson
> Toronto ON
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170109/c6496a84/attachment.html>


  reply	other threads:[~2017-01-09 15:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  2:30 Norman Wilson
2017-01-09  3:31 ` Steve Johnson
2017-01-09 15:30   ` Marc Rochkind [this message]
2017-01-09 15:45     ` arnold
2017-01-09 15:59       ` ron minnich
2017-01-09 16:03       ` Clem Cole
2017-01-10 18:44         ` Lawrence Stewart
2017-01-09 18:48     ` Derek Fawcus
2017-01-09 20:35     ` Steve Johnson
2017-01-10 12:24       ` Tony Finch
2017-01-11  6:00   ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2017-01-10 13:50 Noel Chiappa
2017-01-10  4:40 Rudi Blom
     [not found] <mailman.1.1484013601.5032.tuhs@minnie.tuhs.org>
2017-01-10  3:11 ` Paul McJones
2017-01-09  1:06 Doug McIlroy
2017-01-09  2:18 ` Random832
2017-01-08 20:37 Walter F.J. Mueller
2017-01-08 21:12 ` Larry McVoy
2017-01-08 21:26   ` Dave Horsfall
2017-01-08 21:54 ` Kay Parker   
2017-01-08 23:14 ` Adam Sampson

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='CAOkr1zU=s4uYL6m3AhRz7UcxaGRSrzgaAN5JPukHbw_UVAM_AQ@mail.gmail.com' \
    --to=rochkind@basepath.com \
    /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).