public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsberg@bnl.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/6772: Template-qualified default argument gives parse error
Date: Wed, 22 May 2002 11:36:00 -0000	[thread overview]
Message-ID: <200205221833.g4MIXJnX032035@jsberg1.cap.bnl.gov> (raw)


>Number:         6772
>Category:       c++
>Synopsis:       Template-qualified default argument gives parse error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed May 22 11:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        3.1
>Organization:
>Environment:
System: Linux jsberg1 2.4.18 #1 SMP Fri May 17 19:53:05 EDT 2002 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.1/configure --prefix=/opt/gcc-3.1 --enable-threads
>Description:
If test01.cc is the code given below in How-To-Repeat, then
c++ -Wall -ansi -pedantic -c test01.cc
test01.cc:9: type specifier omitted for parameter `M'
test01.cc:9: parse error before `>' token
	
>How-To-Repeat:
c++ -Wall -ansi -pedantic -c test01.cc

template<typename T, int N> class A {
public:
  static const int i=1;
};

template<typename T, int M> class B {
public:
  void f(int j=A<T,M>::i);
};
	
>Fix:
Workaround: insert parentheses around A<T,M>::i or A<T,M>
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-22 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 11:36 jsberg [this message]
2002-05-23  6:53 lerdsuwa
2003-01-23  2:07 bangerth

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=200205221833.g4MIXJnX032035@jsberg1.cap.bnl.gov \
    --to=jsberg@bnl.gov \
    --cc=gcc-gnats@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).