From: "Douglas A. Gwyn" <dagwyn@home.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installing the updates
Date: Wed, 2 Aug 2000 09:39:05 +0000 [thread overview]
Message-ID: <3987E4B0.FEA6B593@home.com> (raw)
In-Reply-To: <200008011603.MAA05857@egyptian-gods.MIT.EDU>
Greg Hudson wrote:
> a low cost (and one which can be optimized away for ifdef-protected
> headers; I'm told gcc does so).
The general trick is for the preprocessor to maintain
a table of (lock_symbol,header_name) entries, and when
a new header file is read, to make a note whether it
consists of <white>#ifndef symbol...#endif<white>
(after comment processing). If so, the symbol and
file name go into the table. #include processing
always checks the table and if there is an entry for
the file, if the associated lock_symbol is defined,
the file is not even opened. This trick does no harm.
next prev parent reply other threads:[~2000-08-02 9:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 15:15 rob pike
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 [this message]
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=3987E4B0.FEA6B593@home.com \
--to=dagwyn@home.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).