Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!sri-unix!DBrown@HI-MULTICS.ARPA
From: DBrown@HI-MULTICS.ARPA
Newsgroups: net.lang.c
Subject: Re: Declarations and defaulting in C
Message-ID: <1745@sri-arpa.UUCP>
Date: Sun, 8-Jul-84 16:27:00 EDT
Article-I.D.: sri-arpa.1745
Posted: Sun Jul  8 16:27:00 1984
Date-Received: Tue, 10-Jul-84 07:42:43 EDT
Lines: 19


  Not break user code.... hmmn.
  I wonder if the committee might consider publishing a discussion on
how to evolve a language.  Obviously programs with "a =- 3" are broken
by the release of the S5V1 compiler, and I regard this as a good thing.
On the other hand, I'd hate to have to go around rewriting programs
*often* because the language has done a "cobol" and sneaked out from
under my program.  (sneaked?  snuck?  sniggled?  double hmmn).
  I'll volunteer the Multics-ism that if a piece of software is allowed
to upgrade to a non-compatable format for its stored data, then that
program must contain a mechanism for upgrading data from the immediatly
previous version.
  As a Unix-ism this might be stated in the form of a YACC grammar for a
language-upgrading filter to use.
  As always, comments and attacks invited.
   --dave (unix hack on a bun) brown
     DBrown @ HI-Multics.ARPA
     drbrown at watbun.UUCP
     dave @ brown.TSD1.Honeywell