From: Neil Booth <NeilB@earthling.net>
To: Joern Rennecke <amylaar@cygnus.co.uk>
Cc: Jamie Lokier <egcs@tantalophile.demon.co.uk>,
Jan Dvorak <johnydog@go.cz>,
Craig Rodrigues <rodrigc@mediaone.net>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: warning: multi-line comment (why?)
Date: Mon, 25 Sep 2000 15:53:00 -0000 [thread overview]
Message-ID: <20000925235347.A12334@daikokuya.demon.co.uk> (raw)
In-Reply-To: <200009252218.XAA03418@phal.cygnus.co.uk>
Joern Rennecke wrote:-
> > You get diagnostics as reqd by the standard.
>
> Is that with or without a colomn number?
Ah, now I see what you're getting at. The \\n case reports the
beginning of the in-progress token; missing \n reports the col number.
Not sure it's worth changing; it's not as if the location is in any
doubt. Do you think it's worth the extra overhead to get a correctly
reported column number for unexpected EOF?
Neil.
next prev parent reply other threads:[~2000-09-25 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000925230543.A28863@daikokuya.demon.co.uk>
2000-09-25 15:18 ` Joern Rennecke
2000-09-25 15:53 ` Neil Booth [this message]
2000-09-25 16:39 ` Joern Rennecke
2000-09-26 3:43 ` Jamie Lokier
2000-09-26 10:13 ` Neil Booth
2000-09-17 15:53 Craig Rodrigues
2000-09-17 16:12 ` Jan Dvorak
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
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=20000925235347.A12334@daikokuya.demon.co.uk \
--to=neilb@earthling.net \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@tantalophile.demon.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=johnydog@go.cz \
--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).