From: David <david@kdbarto.org>
To: Steve Johnson <scj@yaccman.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Archaic yacc C grammar
Date: Mon, 29 Oct 2018 12:02:29 -0700 [thread overview]
Message-ID: <5DB0D670-6B65-4558-9CCE-7F80FE5B62BA@kdbarto.org> (raw)
In-Reply-To: <068e3163f59e699e486287cf033dc226fbb59b87@webmail.yaccman.com>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
> On Oct 29, 2018, at 10:52 AM, Steve Johnson <scj@yaccman.com> wrote:
>
> We actually had a pretty good system for making changes like that. First, we would change
> the compiler to accept both the old and the new. Then we would produce a warning
> that on a particular date the old would no longer work. Then we made the old an error
> and printed a message about how to fix it. Eventually, we just let it be a syntax error.
> This process was applied many times on the way from typeless B to strongly typed C.
Was there ever a time when a change was desired that you couldn’t accept both
the old and the new?
David
[-- Attachment #2: Type: text/html, Size: 1397 bytes --]
next prev parent reply other threads:[~2018-10-29 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 21:34 Lars Brinkhoff
2018-10-29 3:00 ` Steve Johnson
2018-10-29 7:31 ` Lars Brinkhoff
2018-10-29 17:52 ` Steve Johnson
2018-10-29 18:37 ` Warner Losh
2018-10-30 8:16 ` Lars Brinkhoff
2018-11-03 21:50 ` Steve Johnson
2018-10-29 19:02 ` David [this message]
2018-10-30 22:01 ` Steve Johnson
2018-10-31 0:58 ` Larry McVoy
2018-10-31 13:49 ` Clem Cole
2018-11-03 22:14 ` Steve Johnson
2018-10-31 6:09 ` Lars Brinkhoff
2018-10-31 15:39 Noel Chiappa
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=5DB0D670-6B65-4558-9CCE-7F80FE5B62BA@kdbarto.org \
--to=david@kdbarto.org \
--cc=scj@yaccman.com \
--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).