public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ak@ixion.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/3423: "iterator" name lookup trouble
Date: Tue, 26 Jun 2001 04:36:00 -0000	[thread overview]
Message-ID: <20010625174003.1627.qmail@ixion.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]

>Number:         3423
>Category:       c++
>Synopsis:       "iterator" name lookup trouble
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 26 04:36:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Andreas Klöckner
>Release:        3.0
>Organization:
iXiONmedia
>Environment:
System: Linux dendrite 2.4.4 #4 Don Mai 3 00:14:41 CEST 2001 i586 unknown
Architecture: i586

host: i586-pc-linux-gnu
build: i586-pc-linux-gnu
target: i586-pc-linux-gnu
configured with: ./configure --prefix=/opt/gcc-3.0/
>Description:
#include <vector>
-------------------------------------------------------------------------------
using namespace std;

template <class T>
struct coord_vector {
  };

template<class T>
struct polygon_segment : public vector<coord_vector<T> > {
    void insert_c(iterator it);
  };

-------------------------------------------------------------------------------
	This file results in a parse error in the "insert_c" line, though
	it should probably find the superclass's iterator. The problem goes
	away if coord_vector is a non-template.
>How-To-Repeat:
	
>Fix:
	qualify "iterator" with superclass name
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-26  4:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  4:36 ak [this message]
2001-06-26  5:24 lerdsuwa
2001-06-26  6:06 Artem Khodush

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=20010625174003.1627.qmail@ixion.net \
    --to=ak@ixion.net \
    --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).