From: rob@plan9.research.att.com rob@plan9.research.att.com
Subject: kc & include & comment
Date: Thu, 12 Jan 1995 11:09:44 -0500 [thread overview]
Message-ID: <19950112160944.NUpH8sy5gKMHjpOLQo0tC31mZ7lQzNw4KTnCK-zavmA@z> (raw)
C_Test cat ooh_include.c
#include <u.h> /* failed */
void main(void) {}
It's a silly restriction of the C compilers that it can't handle comments
on preprocessor lines. It should at least be documented.
next reply other threads:[~1995-01-12 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-01-12 16:09 rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-01-12 8:30 Hans-Peter
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=19950112160944.NUpH8sy5gKMHjpOLQo0tC31mZ7lQzNw4KTnCK-zavmA@z \
--to=rob@plan9.research.att.com \
/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).