From: Jan Dvorak <johnydog@go.cz>
To: Craig Rodrigues <rodrigc@mediaone.net>
Cc: gcc@gcc.gnu.org
Subject: Re: warning: multi-line comment (why?)
Date: Sun, 17 Sep 2000 16:12:00 -0000 [thread overview]
Message-ID: <20000918011158.A924@napalm.go.cz> (raw)
In-Reply-To: <20000917185453.A14829@mediaone.net>
On Sun, Sep 17, 2000 at 06:54:53PM -0400, Craig Rodrigues wrote:
> If I have the following code:
> ====================================================================
> // Some comment
> // \
^^
> // Some more comment
>
char '\' at end of line is threaten as that statement is continuing on next
line. '//' comments is mentioned for one line only, and for multiline
comments the right way is '/* */'.
And the warning comes from preprocesor intself - try 'cpp -Wall ./source.c'.
Jan Dvorak <johnydog@go.cz>
next prev parent reply other threads:[~2000-09-17 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-17 15:53 Craig Rodrigues
2000-09-17 16:12 ` Jan Dvorak [this message]
2000-09-17 16:26 ` Richard Henderson
2000-09-18 3:04 ` Jamie Lokier
2000-09-19 9:05 ` Jan Dvorak
2000-09-19 10:13 ` Jamie Lokier
2000-09-19 11:44 ` Jan Dvorak
[not found] ` <20000919214025.A30587@daikokuya.demon.co.uk>
[not found] ` <20000919214320.A30677@daikokuya.demon.co.uk>
2000-09-20 8:52 ` Jamie Lokier
2000-09-20 9:38 ` Neil Booth
2000-09-25 12:52 ` Jamie Lokier
2000-09-25 14:10 ` Neil Booth
2000-09-25 14:34 ` Joern Rennecke
[not found] ` <20000925222224.B24101@daikokuya.demon.co.uk>
[not found] ` <20000926001457.A12405@daikokuya.demon.co.uk>
2000-09-26 10:15 ` Varargs macros subtly broken Jamie Lokier
[not found] <20000925230543.A28863@daikokuya.demon.co.uk>
2000-09-25 15:18 ` warning: multi-line comment (why?) Joern Rennecke
2000-09-25 15:53 ` Neil Booth
2000-09-25 16:39 ` Joern Rennecke
2000-09-26 3:43 ` Jamie Lokier
2000-09-26 10:13 ` Neil Booth
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=20000918011158.A924@napalm.go.cz \
--to=johnydog@go.cz \
--cc=gcc@gcc.gnu.org \
--cc=rodrigc@mediaone.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).