public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rguenth@tat.physik.uni-tuebingen.de
Subject: Re: c++/9407: [3.4 regression] Parser bug
Date: Wed, 22 Jan 2003 21:44:00 -0000	[thread overview]
Message-ID: <20030122214435.29874.qmail@sources.redhat.com> (raw)

Synopsis: [3.4 regression] Parser bug

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Wed Jan 22 21:44:35 2003
State-Changed-Why:
    You need to write
         typename Foo<Dim>::Bar(1);
    (note the "typename").
    
    Also, there is no need to ping gcc@gcc.gnu.org for each bug
    you find. The people who can fix bugs, and the people like
    me who filter them, are quite comfortable with reading
    gcc-bugs (where new reports are automatically posted), and
    with searching the database.
    
    -Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9407


             reply	other threads:[~2003-01-22 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 21:44 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-22 21:16 rguenth

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=20030122214435.29874.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rguenth@tat.physik.uni-tuebingen.de \
    /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).