public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: snyder@fnal.gov To: gcc-gnats@gcc.gnu.org Subject: c++/5796: g++ 3.1: template class problem Date: Thu, 28 Feb 2002 14:36:00 -0000 [thread overview] Message-ID: <200202282059.g1SKxxh07471@karma.fnal.gov> (raw) >Number: 5796 >Category: c++ >Synopsis: g++ 3.1: template class problem >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Thu Feb 28 13:06:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: scott snyder >Release: 3.1 20020227 (prerelease) >Organization: >Environment: System: Linux karma 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../egcs/configure --prefix=/usr/local/egcs --enable-threads=posix --enable-long-long --enable-languages=c,c++,f77 >Description: g++ gives a bogus error message compiling the source below: $ cc1plus -quiet x.cc x.cc: In function `void init_mapping(X<int>*)': x.cc:9: invalid use of undefined type `struct X<int>' x.cc:3: forward declaration of `struct X<int>' Note that the error goes away if the line mapping[0].first = 0; is changed to the equivalent mapping->first = 0; >How-To-Repeat: --------------------------------------------------------------- template <class T> struct X { int first; }; void init_mapping (X<int>* mapping) { mapping[0].first = 0; } --------------------------------------------------------------- >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-02-28 21:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-28 14:36 snyder [this message] 2002-03-03 14:47 nathan
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=200202282059.g1SKxxh07471@karma.fnal.gov \ --to=snyder@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: 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).