From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-28215-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 29899 invoked by alias); 22 Jan 2003 21:44:35 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 29877 invoked by uid 48); 22 Jan 2003 21:44:35 -0000
Date: Wed, 22 Jan 2003 21:44:00 -0000
Message-ID: <20030122214435.29874.qmail@sources.redhat.com>
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
  rguenth@tat.physik.uni-tuebingen.de
From: bangerth@dealii.org
Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, rguenth@tat.physik.uni-tuebingen.de,
  gcc-gnats@gcc.gnu.org
Subject: Re: c++/9407: [3.4 regression] Parser bug
X-SW-Source: 2003-01/txt/msg01254.txt.bz2
List-Id: <gcc-prs.sourceware.org>

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