Re: c++/3063: Explicit specification of a template-argument gives syntax error inside a template function.

[Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>]

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

From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: Martin Sebor <sebor@roguewave.com>
Cc: nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/3063: Explicit specification of a template-argument gives syntax   error inside a template function.
Date: 08 Jun 2001 00:39:20 +0200

 Martin Sebor <sebor@roguewave.com> writes:
 
 | The following reply was made to PR c++/3063; it has been noted by GNATS.
 | 
 | From: Martin Sebor <sebor@roguewave.com>
 | To: pme@gcc.gnu.org
 | Cc: gcc-gnats@gcc.gnu.org
 | Subject: Re: c++/3063: Explicit specification of a template-argument gives syntax 
 |  error inside a template function.
 | Date: Thu, 07 Jun 2001 15:44:48 -0600
 | 
 |  pme@gcc.gnu.org wrote:
 |  > 
 |  > Synopsis: Explicit specification of a template-argument gives syntax error inside a template function.
 |  > 
 |  > State-Changed-From-To: open->closed
 |  > State-Changed-By: pme
 |  > State-Changed-When: Thu Jun  7 14:35:40 2001
 |  > State-Changed-Why:
 |  > 
 |  >     Not a bug.  The parser thinks that < means 'less than'.
 |  >     You're required by the c++ standard to write
 |  > 
 |  >         a.template func<char>();     // line 15
 |  
 |  Only in a dependent context. `a' here doesn't depend on a template
 |  parameter so `template' isn't required. I believe this is a known
 |  bug in the parser (someone else acknowledged it on this list in
 |  the past).
 
 Yes, that is a known bug, as I said a similar bug report.
 
 -- Gaby