From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installing the updates
Date: Mon, 31 Jul 2000 11:15:35 -0400 [thread overview]
Message-ID: <200007311515.LAA18248@cse.psu.edu> (raw)
> In one of my porting project, <stdio.h> is included twice.
Pardon me for doing a boyd here, but you only need to include
it once - you get everything defined the first time.
Seriously, we deliberately refused to buy into that multiple
inclusion dance, which is a hideous non-solution for the problem
of undefined dependency order on #includes. Why not use the
occasion to clean up the code so you only include <stdio.h> once?
I'll let Russ answer your wrap questions; he's the author.
-rob
next reply other threads:[~2000-07-31 15:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 15:15 rob pike [this message]
2000-08-01 8:53 ` Douglas A. Gwyn
2000-08-01 12:12 ` Howard Trickey
2000-08-02 9:11 ` Douglas A. Gwyn
2000-08-01 14:31 ` Ralph Corderoy
2000-08-01 16:03 ` Greg Hudson
2000-08-01 16:32 ` James A. Robinson
2000-08-01 17:05 ` James A. Robinson
2000-08-02 9:39 ` Douglas A. Gwyn
2000-08-02 9:11 ` Douglas A. Gwyn
2000-08-03 14:51 ` ozan s. yigit
-- strict thread matches above, loose matches on Subject: below --
2000-08-02 9:47 forsyth
2000-08-02 9:52 ` Boyd Roberts
2000-08-01 17:06 Russ Cox
2000-08-02 8:32 ` Bruce G. Stewart
2000-08-01 16:27 rob pike
2000-08-02 10:53 ` Ralph Corderoy
2000-08-01 16:26 rob pike
2000-08-02 21:49 ` Steve Simon
2000-08-01 13:35 rob pike
2000-08-01 18:34 ` Greg Hudson
2000-08-02 9:53 ` Douglas A. Gwyn
2000-08-01 13:06 rob pike
2000-08-01 13:10 ` Lucio De Re
2000-08-01 12:55 rob pike
2000-08-02 9:39 ` Douglas A. Gwyn
2000-08-01 6:04 Russ Cox
2000-08-01 5:42 Russ Cox
2000-07-31 17:09 Russ Cox
2000-07-31 15:57 jmk
[not found] <djhender@telusplanet.net>
2000-07-31 14:53 ` Doug Henderson
2000-07-31 17:38 ` Scott Schwartz
2000-07-31 20:10 ` Steve Simon
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=200007311515.LAA18248@cse.psu.edu \
--to=rob@plan9.bell-labs.com \
--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).