9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9's C compiler and // comments
Date: Mon, 15 Sep 2003 01:01:26 -0700	[thread overview]
Message-ID: <e9e7ab639fcd75a9dc076da42ae1085b@collyer.net> (raw)
In-Reply-To: <01a201c37b5d$f612ad60$b9844051@insultant.net>

cpp gets abused, but we need it (or m4 or something of the sort), if
only for #include, so it's not completely unnecessary.  The bad old
days, when we walked 5 miles uphill to and from school, were not
pretty: when cpp was an optional compiler pass and /usr/include didn't
exist yet, only the kernel bothered to #include headers, and the
number of bugs in V6 Unix programs because somebody had copied a
struct declaration out of a manual page and then the real struct
changed (or they had copied it incorrectly in the first place) was
considerable.



  reply	other threads:[~2003-09-15  8:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  3:06 David Presotto
2003-09-15  3:14 ` mirtchov
2003-09-15  3:19   ` David Presotto
2003-09-15  7:11     ` Charles Forsyth
2003-09-15  7:51   ` boyd, rounin
2003-09-15  8:23   ` boyd, rounin
2003-09-15  3:21 ` Bruce Ellis
2003-09-15  8:00   ` boyd, rounin
2003-09-15  4:06 ` Enache Adrian
2003-09-15  7:03   ` Charles Forsyth
2003-09-15  7:49 ` boyd, rounin
2003-09-15  8:01   ` Geoff Collyer [this message]
     [not found] <1630899296@snellwilcox.com>
2003-09-15 11:01 ` steve.simon
2003-09-15 11:23   ` C H Forsyth
2003-09-15 11:26   ` C H Forsyth
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15  1:02 David Presotto
2003-09-15  1:16 ` Enache Adrian
2003-09-15  1:23   ` boyd, rounin
2003-09-15  7:21     ` Charles Forsyth
2003-09-15  2:21   ` Enache Adrian
2003-09-15  0:49 Enache Adrian

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=e9e7ab639fcd75a9dc076da42ae1085b@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).