public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: joerg@eyematic.com To: gcc-gnats@gcc.gnu.org Subject: c++/6284: iterator type definitions not accessible in derived template classes Date: Fri, 12 Apr 2002 14:46:00 -0000 [thread overview] Message-ID: <20020412214302.30448.qmail@sources.redhat.com> (raw) >Number: 6284 >Category: c++ >Synopsis: iterator type definitions not accessible in derived template classes >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Apr 12 14:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: joerg@eyematic.com >Release: g++-3.0.3 >Organization: >Environment: i686-pc-linux-gnu >Description: The following code does not compile. The problem is the iterator used in the print() function. After close examination, we noticed that if we explicitely define the iterator with a typedef as is done in std_list.h for the list template definition, the problem goes away. Here the example: ======================================================== #include <iostream> #include <list> using namespace std; template <class type> class my_list : public list<type> { public: void print() const; }; template <class type> void my_list<type>::print() const { list<type>::const_iterator i; for( i = begin(); i != end(); i++ ) { cout << *i; } } /**/ int main() { my_list<int> l; l.push_back( 1 ); l.print(); } >How-To-Repeat: To reproduce the problem, compile with g++ -pedantic t.cpp -o t where t.cpp contains the example code above. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-04-12 21:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-12 14:46 joerg [this message] 2002-04-12 14:58 pme
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=20020412214302.30448.qmail@sources.redhat.com \ --to=joerg@eyematic.com \ --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).