public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8237: parse error for legal code - works on intel and solaris compilers
Date: Tue, 15 Oct 2002 17:16:00 -0000	[thread overview]
Message-ID: <20021016001602.5223.qmail@sources.redhat.com> (raw)

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

From: Phil Edwards <phil@jaj.com>
To: joel.zuhars@med.ge.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/8237: parse error for legal code - works on intel and solaris compilers
Date: Tue, 15 Oct 2002 20:10:57 -0400

 On Tue, Oct 15, 2002 at 10:51:55PM -0000, joel.zuhars@med.ge.com wrote:
 > >Description:
 > Hello, the following simple code gives a parse error when compiling
 > with g++, but works on both intel and solaris compilers. Is it a bug,
 > or am I just missing something obvious? Thanks for any help.
 
 Go to
 
     http://gcc.gnu.org/bugs.html#known
 
 and scroll all the way down to "parse errors for simple code" for some
 possible workarounds.  As Gabriel says, this should be fixed in the ongoing
 parser rewrite.
 
 -- 
 I would therefore like to posit that computing's central challenge, viz. "How
 not to make a mess of it," has /not/ been met.
                                                  - Edsger Dijkstra, 1930-2002


             reply	other threads:[~2002-10-16  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 17:16 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-01 14:09 neroden
2002-10-15 16:16 Gabriel Dos Reis
2002-10-15 16:09 gdr
2002-10-15 15:56 joel.zuhars

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=20021016001602.5223.qmail@sources.redhat.com \
    --to=phil@jaj.com \
    --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).