From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9's C compiler and // comments
Date: Mon, 15 Sep 2003 08:21:48 +0100 [thread overview]
Message-ID: <46a49abf9f3cb8bedf2a83b89dff8fcc@caldo.demon.co.uk> (raw)
In-Reply-To: <016f01c37b27$e920fca0$b9844051@insultant.net>
>>things were not helped by the complexity of the reiser cpp either.
the remarkable thing is that later work on C ADDED to the preprocessor,
and even more later!
``when you're in a hole ...''
fortunately, it must be said that even in some of the worst code i've seen
the authors kept to the simpler constructions. the main problems in practice
tend to be the use of it at all (eg, Linux enumerating arbitrarily many platforms in a single file
controlled by #ifdef!), and overly complex #if expressions (which, not being
checked much can easily go wrong). a little gem recently was ``#if ndef ...''.
next prev parent reply other threads:[~2003-09-15 7:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-09-15 2:21 ` Enache Adrian
[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 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
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=46a49abf9f3cb8bedf2a83b89dff8fcc@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).