public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Monteiro Basso <dmbasso@zaz.com.br>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10120: single-line comment interfering in the next line
Date: Mon, 17 Mar 2003 19:46:00 -0000	[thread overview]
Message-ID: <20030317194600.10602.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10120; it has been noted by GNATS.

From: Daniel Monteiro Basso <dmbasso@zaz.com.br>
To: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc: Rafael Jannone <jannone@inf.ufrgs.br>
Subject: Re: c++/10120: single-line comment interfering in the next line
Date: Mon, 17 Mar 2003 16:39:25 -0300

 00000710  7d 20 2f 2f 45 52 52 4f  52 20 43 4f 4d 4d 45 4e  |} //ERROR COMMEN|
 00000720  54 0d 20 20 20 20 20 20  6f 70 65 72 61 74 6f 72  |T.      operator|
 
 No, it does not have CR/LF. I know 3.x handles the problem, I have 3.0 and 3.2 installed too, but shouldn't this thing be corrected in 2.95?
 
 Thanx,
 
 Daniel
 
 neil@gcc.gnu.org wrote:
 > Synopsis: single-line comment interfering in the next line
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: neil
 > State-Changed-When: Mon Mar 17 08:27:12 2003
 > State-Changed-Why:
 >     You had an MSDOG line ending.  3.x handles these properly.
 > 
 
 -- 
 *** It's GNU/Linux dammit! ***


             reply	other threads:[~2003-03-17 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 19:46 Daniel Monteiro Basso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-17 20:16 DJ Delorie
2003-03-17  8:31 neil
2003-03-17  7:06 dmbasso

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=20030317194600.10602.qmail@sources.redhat.com \
    --to=dmbasso@zaz.com.br \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).