public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/100: [parser] confusing name lookup diagnostic
Date: Fri, 16 Nov 2001 18:06:00 -0000	[thread overview]
Message-ID: <20011121105602.13433.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/100; it has been noted by GNATS.

From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org, snyder@fnal.gov
Cc:  
Subject: Re: c++/100: [parser] confusing name lookup diagnostic
Date: 21 Nov 2001 10:49:16 -0000

 Old Synopsis: confusing name lookup diagnostic
 New Synopsis: [parser] confusing name lookup diagnostic
 
 State-Changed-From-To: analyzed->suspended
 State-Changed-By: nathan
 State-Changed-When: Wed Nov 21 02:49:12 2001
 State-Changed-Why:
     The cp-parser branch reports,
     incomming/100.ii:10: use of `CftCluster' is ambiguous
     incomming/100.ii:1:   first declared as `class CftCluster' here
     incomming/100.ii:4:   also declared as `typedef class CftCluster d0track::CftCluster' here
     incomming/100.ii:10: `CftCluster' denotes an ambiguous type
     incomming/100.ii:1:   first type here
     incomming/100.ii:1:   other type here
     incomming/100.ii:10: `CftCluster' undeclared (first use this function)
     incomming/100.ii:10: (Each undeclared identifier is reported only once for each function it appears in.)
     incomming/100.ii:10: expected `;'
     which is still wrong, but I'm suspending this until that
     branch is folded into the mainline
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=100&database=gcc


             reply	other threads:[~2001-11-21 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 18:06 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 19:20 nathan
2002-12-31 16:58 neil
2001-11-16 18:02 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=20011121105602.13433.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).