public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gjlos@rz.uni-mannheim.de To: gcc-gnats@gcc.gnu.org Subject: c++/3531: namespace lookup for template specialization fails <synopsis of the problem (one line)> Date: Mon, 02 Jul 2001 09:26:00 -0000 [thread overview] Message-ID: <200107021623.SAA27584@memorum.rz.uni-mannheim.de> (raw) >Number: 3531 >Category: c++ >Synopsis: namespace lookup for template specialization fails >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Mon Jul 02 09:26:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Gert-jan Los >Release: 3.0 >Organization: >Environment: System: SunOS memorum 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-1 Architecture: sun4 host: sparc-sun-solaris2.7 build: sparc-sun-solaris2.7 target: sparc-sun-solaris2.7 configured with: ../gcc-3.0/configure --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-nls --disable-threads --enable-languages=c,c++ >Description: Given the code below. g++ rejects the specialization of ns::foo<true> despite the explicit namespace qualification. The Message reads: ns_templspec.C:5: specializing `struct ns::foo<true>' in different namespace ns_templspec.C:2: from definition of `template<bool FLAG> struct ns::foo' >How-To-Repeat: cat <<-'EOT' >ns_templspec.C namespace ns { template<bool FLAG> struct foo; } template<> struct ns::foo<true> { }; EOT g++ ns_templspec.C >Fix: Rewrite the last line as namespace ns { template<> struct foo<true> { }; } >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-07-02 9:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200107021623.SAA27584@memorum.rz.uni-mannheim.de \ --to=gjlos@rz.uni-mannheim.de \ --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: linkBe 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).