public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: derrick@cco.caltech.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/10852: Old for-scoping rules improperly used?
Date: Mon, 19 May 2003 07:46:00 -0000	[thread overview]
Message-ID: <20030519074144.20364.qmail@sources.redhat.com> (raw)


>Number:         10852
>Category:       c++
>Synopsis:       Old for-scoping rules improperly used?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon May 19 07:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Derrick Bass
>Release:        gcc-3.3
>Organization:
>Environment:

>Description:
I think this is a bug in g++; but there is always the possibility that it is a bug in my understanding of C++. In the following code gcc assumes that the variable i at the end of function is the same as in the for loop and produces the following error:
nstest.cc: In function `void f()':
nstest.cc:9: error: name lookup of `i' changed for new ISO `for' scoping
nstest.cc:6: error:   using obsolete binding at `i'

I think it should use the variable i from inside the namespace and quit complaining, but as I said, I may just be misunderstanding C++ arcana.

Here's the sample code...
namespace X {
  int i;
}

void f() {
  for (int i=0; i<10; ++i)
    ;
  using namespace X;
  i;
}
>How-To-Repeat:

>Fix:
Workaround is to replace "using namespace X" with "using X::i"
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-05-19  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  7:46 derrick [this message]
2003-05-19  8:32 Gabriel Dos Reis
2003-05-19 14:12 bangerth

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=20030519074144.20364.qmail@sources.redhat.com \
    --to=derrick@cco.caltech.edu \
    --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).