public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philip Martin <philip@codematters.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7049 Overloading "cout <<" in one namespace obscures similar functions in a different namespace
Date: Tue, 18 Jun 2002 04:46:00 -0000	[thread overview]
Message-ID: <20020618113603.791.qmail@sources.redhat.com> (raw)

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

From: Philip Martin <philip@codematters.co.uk>
To: steev@paradigmds.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/7049 Overloading "cout <<" in one namespace obscures similar functions in a different namespace
Date: 18 Jun 2002 12:30:14 +0100

 This is not a bug, that's how name lookup works.
 
 The compiler will lookup operator<< in the anonymous namespace where
 the statement "cout << x" occurs, the std:: namespace where ostream is
 defined, and the ns:: namespace where class X is defined.  Since the
 compiler will find an operator<< by doing this it won't look anywhere
 else.  In particular operator<< in the global namespace will not be
 considered.
 
 Put operator<< for X where it belongs, in the ns:: namespace that
 defines class X.
 
 -- 
 Philip


             reply	other threads:[~2002-06-18 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18  4:46 Philip Martin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-18  6:06 c++/7049: " paolo
2002-06-17  5:10 paolo
2002-06-17  2:16 paolo
2002-06-17  2:13 steev

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=20020618113603.791.qmail@sources.redhat.com \
    --to=philip@codematters.co.uk \
    --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).