public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jlawson-gcc@bovine.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/10174: g++ wrongly assumes a namespace of a function based on the namespace of the function's argument
Date: Fri, 21 Mar 2003 00:26:00 -0000	[thread overview]
Message-ID: <20030321002321.17724.qmail@sources.redhat.com> (raw)


>Number:         10174
>Category:       c++
>Synopsis:       g++ wrongly assumes a namespace of a function based on the namespace of the function's argument
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 21 00:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     jlawson-gcc@bovine.net
>Release:        g++ (GCC) 3.2
>Organization:
>Environment:
Linux redhat 7.2, (Red Hat Linux Rawhide g++ 3.2-1)
>Description:
g++ compiles the attached example, even though I don't think the compiler should assume the scope of the bork() function.

g++ does not assume the scope of the function if it does not take an argument that also a member of that namespace.
>How-To-Repeat:
g++ testnamespace.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="testnamespace.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="testnamespace.cpp"

bmFtZXNwYWNlIG1vbyB7CiAgICBzdHJ1Y3QgY293IHsKICAgICAgICBpbnQgYXNkZjsKICAgIH07
CiAgICAKICAgIHZvaWQgYm9yayhtb286OmNvdywgaW50IGkpIHt9Cn0KCnZvaWQgZG9pdCgpCnsK
ICAgIG1vbzo6Y293IHZhcjsKICAgIHZhci5hc2RmID0gMTsKCiAgICBib3JrKHZhciwgMSk7IC8v
IHNob3VsZCByZXF1aXJlIG1vbzo6Ym9yayh2YXIpCn0K


             reply	other threads:[~2003-03-21  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21  0:26 jlawson-gcc [this message]
2003-03-21  0:32 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=20030321002321.17724.qmail@sources.redhat.com \
    --to=jlawson-gcc@bovine.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).