From: Andrew Pochinsky <avp@honti.mit.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Design choice is C preprocessor
Date: Mon, 23 Apr 2001 18:12:51 -0400 [thread overview]
Message-ID: <200104232212.f3NMCpq12483@honti.mit.edu> (raw)
A historical question: What were reasons for #include to stand alone
on a line? It seems that allowing #include "filename" anywhere does
not change much the implementation, while imposing less restrictions
on the programmer.
--andrew
next reply other threads:[~2001-04-23 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 22:12 Andrew Pochinsky [this message]
2001-04-25 1:34 ` Boyd Roberts
2001-04-25 8:15 ` Re[2]: " matt
2001-04-26 3:10 ` Boyd Roberts
2001-04-26 7:29 ` Re[4]: " matt
2001-04-26 8:24 ` Boyd Roberts
2001-04-26 10:32 ` nospam
2001-04-26 13:20 ` Boyd Roberts
2001-04-26 13:48 presotto
2001-04-26 15:35 ` Douglas A. Gwyn
2001-04-26 23:06 Re[4]: " Boyd Roberts
2001-04-26 23:28 ` Andrey A Mirtchovski
2001-04-27 14:40 ` Douglas A. Gwyn
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=200104232212.f3NMCpq12483@honti.mit.edu \
--to=avp@honti.mit.edu \
--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).