public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: James E Wilson <wilson@specifixinc.com>
To: "R. Clayton" <rclayton@monmouth.edu>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: Possible g++ compilation problem.
Date: Mon, 16 Aug 2004 21:42:00 -0000 [thread overview]
Message-ID: <41212A48.9070609@specifixinc.com> (raw)
In-Reply-To: <200408121649.i7CGnPcU012851@clayton.cs.monmouth.edu>
R. Clayton wrote:
> $ g++ -c junk.cc
> junk.cc: In function `void f(T, ast_node)':
> junk.cc:10: error: syntax error before `>' token
I tried gcc-3.4. It compiles without complaint, so apparently this is
already fixed. gcc-3.4 has rewritten C++ parser, and this fixed many
C++ parsing problems with gcc-3.3 and earlier.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2004-08-16 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 16:49 R. Clayton
2004-08-16 21:42 ` James E Wilson [this message]
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=41212A48.9070609@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=rclayton@monmouth.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 read-only IMAP folder(s) and NNTP newsgroup(s).