public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rhauser@fnal.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/6601: Parse error when using :: qualified name in template.
Date: Tue, 07 May 2002 15:26:00 -0000	[thread overview]
Message-ID: <200205072225.g47MP1k20660@wensley-clued0.fnal.gov> (raw)


>Number:         6601
>Category:       c++
>Synopsis:       Parse error when using :: qualified name in template.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 15:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Reiner Hauser
>Release:        3.0.2
>Organization:
Michigan State University
>Environment:
Linux RedHat 7.1 with local changes
System: Linux wensley-clued0 2.4.14-0.1XFSsmp #1 SMP Mon Nov 12 09:22:08 CST 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ./configure --prefix=/scratch/1/veseli/gcc --with-gnu-as --with-gnu-ld --enable-shared --enable-threads --enable-languages=c,c++
>Description:
	When instantiating a template class with a another class qualified
with :: the compiler reports a parse error. This is true both for standard
templates like vector or user defined templates.

>How-To-Repeat:
	
	template<class T>
	class MyTemplate
	{
	};
	
	class X {};
	
	MyTemplate<::X> test;
	
>Fix:
	Replacing ::X with 'class ::X' allows to work around the problem.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-07 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 15:26 rhauser [this message]
2002-05-14  7:53 lerdsuwa

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=200205072225.g47MP1k20660@wensley-clued0.fnal.gov \
    --to=rhauser@fnal.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).