From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tuhs-bounces@minnie.tuhs.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 2e7e1256 for ; Mon, 29 Oct 2018 20:06:59 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 32B4CA220D; Tue, 30 Oct 2018 06:06:58 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 71AE8A1FB3; Tue, 30 Oct 2018 06:06:44 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=permerror (0-bit key) header.d=smtpservice.net header.i=@smtpservice.net header.b=i3yo/DrV; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id EC7D4A1FB3; Tue, 30 Oct 2018 05:02:38 +1000 (AEST) Received: from a1i214.smtp2go.com (a1i214.smtp2go.com [43.228.184.214]) by minnie.tuhs.org (Postfix) with ESMTPS id 96BB0A1FB0 for ; Tue, 30 Oct 2018 05:02:33 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpservice.net; s=m33y30.a1-4.dyn; x=1540840653; h=Feedback-ID: X-Smtpcorp-Track:To:Message-Id:Reply-To:Date:From:Subject:Sender: List-Unsubscribe; bh=NBGn6NPFbCdGYRBsb2KFQroGkjuPwDMp2apXwxcDnqk=; b=i3yo/DrV 4Iw+dX/WdzafbDxOXSltsdSp/dhSaXETSju3WWYz84/3n6eZJS+tA+1xfu4ytWpf+IdQ8Cx6XR/Kw VHkZsTjhXZgb174UQI7Ivyp0cs9O2aAJ7vk1JqWI4+CGDsMimm/rvlqhZ4O6JCoVBi8mjsHNtPqKO nk3cdQ5ZEBv8iE+H+a+B/rzuoIp+VdgaSyjq1GzVhd9SgBq8tubAtsDGLRFHHeYN7ssLvA9NP2/yp jo+c7PpH/vKpEkRj+/vN55xMVJQkDfmvPREPKgWT/rDmMcZBCPqVd3yc1onw8zPb4Q/0RfsxHzRgS hfuTswAB843p3JbmNpo1E/UN/g==; Received: from [10.45.79.71] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1gHCo3-WxjxSb-UY; Mon, 29 Oct 2018 19:02:31 +0000 Received: from [10.107.193.50] (helo=kdbarto.org) by smtpcorp.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.91) (envelope-from ) id 1gHCo3-DuuarV-2M; Mon, 29 Oct 2018 19:02:31 +0000 Received: from [192.168.2.10] (unknown [192.168.2.10]) by kdbarto.org (Postfix) with ESMTPS id 8EEC8EB3976; Mon, 29 Oct 2018 12:02:29 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_7D3FE8DA-5419-4ABE-9262-9FBFAE73E299" From: David In-Reply-To: <068e3163f59e699e486287cf033dc226fbb59b87@webmail.yaccman.com> Date: Mon, 29 Oct 2018 12:02:29 -0700 Message-Id: <5DB0D670-6B65-4558-9CCE-7F80FE5B62BA@kdbarto.org> References: <068e3163f59e699e486287cf033dc226fbb59b87@webmail.yaccman.com> To: Steve Johnson X-Mailer: Apple Mail (2.3124) X-Smtpcorp-Track: 1gHCo3DIIarV2u.12_GrO8Zb Feedback-ID: 145083m:145083a-yaNWS:145083sbejubOob7 X-Report-Abuse: Please forward a copy of this message, including all headers, to Subject: Re: [TUHS] Archaic yacc C grammar X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: david@kdbarto.org Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --Apple-Mail=_7D3FE8DA-5419-4ABE-9262-9FBFAE73E299 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Oct 29, 2018, at 10:52 AM, Steve Johnson wrote: >=20 > 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=E2=80=99t = accept both the old and the new? David --Apple-Mail=_7D3FE8DA-5419-4ABE-9262-9FBFAE73E299 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
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=E2=80=99t = accept both
the old and the new?

David

= --Apple-Mail=_7D3FE8DA-5419-4ABE-9262-9FBFAE73E299--