The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (norman@nose.cs.utoronto.ca)
Subject: [TUHS] So now that the source is finally out...
Date: Sun, 27 Jan 2002 14:03:40 -0500	[thread overview]
Message-ID: <200201271904.FAA17642@guardian-ext.bond.edu.au> (raw)

Ken Wellsch:

  I'm fairly sure things like "=+" and so on were replaced with "+="
  in the move from V6 to V7.  I think structure assignments were added
  here too, and the much more obscure, being able to declare passed
  arguments in the function preamble as "register."  I believe K&R
  reflects the C language as seen with V7...

The V7 C compiler accepted =+, but it still accepted += as well; there was
a lot of code written the old way, and nobody wanted to be forced to convert
everything all at once.  Similarly, the V7 compiler complained about implicit
conversions between pointers of different types, or between ints and pointers,
but they were treated as warnings, not fatal errors; you could still compile
old code and just ignore the compiler's fussing.

I recall that when I arrived at Bell Labs in 1984, it was apparently not long
after the research group's C compiler had been changed to treat all the
obsolete stuff as errors; certainly there was still code in /usr/src that
hadn't been updated, and all of it had been recompiled recently to run on
the VAX.

A modern C compiler would choke even on some of the stuff that was legal
in those days.  Recently I recompiled tbl with lcc, and had a grand time
cleaning out all the ideas we all thought were clever in the late 1970s
but most of us would never think of doing now.  For those with the virgin
source handy, take a look at subroutine `point' and the way it is used
and abused.

Norman Wilson



             reply	other threads:[~2002-01-27 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-27 19:03 norman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31  1:03 John Holden
2002-01-30  1:40 Ken Wellsch
2002-01-26 14:50 Ken Wellsch
2002-01-27 23:58 ` Greg Lehey
2002-01-31  0:29   ` Joerg Micheel
2002-01-25 19:18 Carl Lowenstein
2002-01-24 18:39 Rob Becker
2002-01-25  9:42 ` P.A.Osborne
2002-01-25 10:27   ` M. Warner Losh
2002-01-25 11:16     ` P.A.Osborne
2002-01-25 15:19       ` Ephrem Hugh Bensusan
2002-01-25 15:52         ` M. Warner Losh
2002-01-25 21:08           ` David C. Jenner
2002-01-25 16:24       ` Wolfgang Rupp
2002-01-29  6:17         ` M. Warner Losh
2002-01-25 16:30       ` Wolfgang Rupp
2002-01-25 17:30   ` Jeffrey S. Sharp

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=200201271904.FAA17642@guardian-ext.bond.edu.au \
    --to=norman@nose.cs.utoronto.ca \
    /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).