From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9's C compiler and // comments
Date: Mon, 15 Sep 2003 13:21:42 +1000 [thread overview]
Message-ID: <00e801c37b38$809aa7b0$c901a8c0@cc77109e> (raw)
In-Reply-To: <4474ff21207aa9cf44a6e3f715f6b492@plan9.bell-labs.com>
I did the special /**/ stuff because some crappy code depends on
them being elided. I probably should have done // as well but
decided not to for some reason lost in the past.
brucee
----- Original Message -----
From: "David Presotto" <presotto@closedmind.org>
To: <enache@rdslink.ro>; <9fans@cse.psu.edu>
Sent: Monday, September 15, 2003 1:06 PM
Subject: Re: [9fans] plan9's C compiler and // comments
> 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.
>
> The // at the end of your endif makes it through only because everything after the
> endif is ignored.
next prev parent reply other threads:[~2003-09-15 3:21 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 [this message]
2003-09-15 8:00 ` boyd, rounin
2003-09-15 4:06 ` Enache Adrian
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='00e801c37b38$809aa7b0$c901a8c0@cc77109e' \
--to=brucee@chunder.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).