The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: arnold@skeeve.com
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Tue, 10 Jul 2018 16:09:34 +1000	[thread overview]
Message-ID: <CAKr6gn1mvPkqafDw6=4VDNh9cuf1CJY6hq1KY6Dz1K5fgOZF9A@mail.gmail.com> (raw)
In-Reply-To: <201807100554.w6A5s0VM005631@freefriends.org>

... and then somebody GNUified it. I seem to recall three huge
flamewars in UUCP days: RFS vs NFS, STREAMS (the original) vs sockets,
and getopt

--no -noo --nooo=please --dont-make-me=do-that

On Tue, Jul 10, 2018 at 3:54 PM,  <arnold@skeeve.com> wrote:
> Clem Cole <clemc@ccc.com> wrote:
>
>> BY the time dmr adds stdio, it was
>> still early enough in the life to displace the randomness for something as
>> important as I/O, whereas lack of use of something.like getopt would not
>> become clearly deficient until after widespread success.
>
> I think "widespread access" is more like it for getopt.  Getopt dates
> to 1980; it was in System III (I just checked). That's only about two years
> after V7 which was circa 1978.
>
> Here are the dates:
>
> -rw-rw-r-- 1 arnold arnold 1073 Apr 11  1980 usr/src/lib/libc/pdp11/gen/getopt.c
> -rw-rw-r-- 1 arnold arnold 2273 May 16  1980 usr/src/man/man3/getopt.3c
>
> But the world outside the Bell System didn't have System III. Getopt
> didn't become "popular" until System V or so, and became much easier to
> adopt once Henry Spencer published his public domain rewrite of the code
> and man page.
>
> Just a nit, (:-)
>
> Arnold

  reply	other threads:[~2018-07-10  6:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51   ` John P. Linderman
2018-06-30  0:50   ` Steve Johnson
2018-06-30 11:44     ` Arrigo Triulzi
2018-06-30 22:42       ` Arthur Krewat
2018-06-30 23:29         ` Arrigo Triulzi
2018-07-01  4:17           ` Larry McVoy
2018-07-01 11:42           ` ron
2018-07-01  5:29       ` Dave Horsfall
2018-07-01  8:28         ` Arrigo Triulzi
2018-07-01 11:34         ` ron
2018-07-09 16:30           ` Random832
2018-07-09 17:13             ` Clem Cole
2018-07-10  5:54               ` arnold
2018-07-10  6:09                 ` George Michaelson [this message]
2018-07-10  7:19                   ` arnold
2018-07-11  0:20                     ` Noel Hunt
2018-07-11  1:31                       ` Larry McVoy
2018-07-11  1:37                         ` George Michaelson
2018-07-11  1:37                         ` ron minnich
2018-07-11  3:12                           ` Larry McVoy
2018-07-11  3:34                         ` [TUHS] getopt (was " Bakul Shah
2018-07-13  9:08                       ` [TUHS] " ches@Cheswick.com
2018-07-13 14:10                         ` ron
2018-07-10 14:10                 ` Clem Cole
2018-07-03 17:34       ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30  0:06   ` Greg 'groggy' Lehey
2018-06-30 14:20   ` John P. Linderman
2018-06-30  1:31 Larry McVoy
2018-06-30  1:45 ` Jon Forrest
2018-06-30 18:43   ` Steve Johnson
2018-07-01 16:35 Norman Wilson
2018-07-02 19:55 Paul Ruizendaal
2018-07-03  7:27 arnold
2018-07-18  9:42 Hendrik Jan Thomassen

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='CAKr6gn1mvPkqafDw6=4VDNh9cuf1CJY6hq1KY6Dz1K5fgOZF9A@mail.gmail.com' \
    --to=ggm@algebras.org \
    --cc=arnold@skeeve.com \
    --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).