The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] FreeBSD retires gets()!
Date: Wed, 27 Nov 2019 08:31:29 +1000	[thread overview]
Message-ID: <CAKr6gn337HzvvtBtxEW-kQ9Do3r_Jp7QuQrf9a8uo2UNwAUJvQ@mail.gmail.com> (raw)
In-Reply-To: <1574805575.17040.for-standards-violators@oclsc.org>

I have managed to forget most of my C issues, but "does it gobble the
\n or does it leave the \n" sticks, because gets() was bound into it,
and because Python perpetuates it in line-mode reading.

On Wed, Nov 27, 2019 at 8:00 AM Norman Wilson <norman@oclsc.org> wrote:
>
> We retired gets from Research UNIX back in 1984 or perhaps
> earlier, with no serious pain because replacing it wasn't
> hard and everybody agreed with the reason.
>
> I'm glad to hear some part of the rest of the world is
> catching up.
>
> We also decided to retire the old Enigma-derived crypt(1),
> except we didn't want to throw it out entirely in case
> someone had an old encrypted file and wanted the contents
> back.  So it was removed from the manual and the binary
> moved to /usr/games.
>
> Norman Wilson
> Toronto ON

  reply	other threads:[~2019-11-26 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 21:59 Norman Wilson
2019-11-26 22:31 ` George Michaelson [this message]
2019-11-26 22:32 ` Dave Horsfall
2019-11-26 23:29   ` Richard Salz
2019-11-27  0:29     ` Dave Horsfall
2019-11-26 23:06 ` Katherine Barto
  -- strict thread matches above, loose matches on Subject: below --
2019-11-26 21:10 Dave Horsfall

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=CAKr6gn337HzvvtBtxEW-kQ9Do3r_Jp7QuQrf9a8uo2UNwAUJvQ@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=norman@oclsc.org \
    --cc=tuhs@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).