From: Enache Adrian <enache@rdslink.ro>
To: 9fans@cse.psu.edu
Cc: enache@rdslink.ro
Subject: Re: [9fans] plan9's C compiler and // comments
Date: Mon, 15 Sep 2003 07:06:37 +0300 [thread overview]
Message-ID: <20030915040637.GA1376@ratsnest.hole> (raw)
In-Reply-To: <4474ff21207aa9cf44a6e3f715f6b492@plan9.bell-labs.com>
On Sun, Sep 14, 2003 a.d., David Presotto wrote:
> Looks like just the opposite to me. /**/ comments are handled specially.
> The prepocessor doesn't know anything about // comments. If you want to
> change it, I wouldn't mind. I think nobody ever thought of or cared to
> do it before because we frown so much on programming with the preprocessor.
Never mind. I stumbled on this when trying to get stuff cut-n-pasted
from external headers working.
I actually fixed that issue with sed.
This should be probably changed only if the compiler is ported outside
plan9 (to make it work like MSVC or gcc, in order to avoid gratuitous
incompatibilities -- but then the whole '#if A && defined(B)' madness
should be probably put in too).
Regards,
Adi
next prev parent reply other threads:[~2003-09-15 4:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-09-15 7:03 ` Charles Forsyth
2003-09-15 7:49 ` boyd, rounin
2003-09-15 8:01 ` Geoff Collyer
[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 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
2003-09-15 2:21 ` Enache Adrian
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=20030915040637.GA1376@ratsnest.hole \
--to=enache@rdslink.ro \
--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).