public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13594] New: namespace association vs. templates part two
Date: Wed, 07 Jan 2004 03:06:00 -0000	[thread overview]
Message-ID: <20040107030635.13594.bkoz@gcc.gnu.org> (raw)

From:
http://gcc.gnu.org/ml/libstdc++/2004-01/msg00047.html

Ugh, more namespace association fallout. It looks like associated namespaces are
not being considered matches. This is probably related to (or the same as) the
other namespace association issue w/ std::swap that Richard Sandiford found.


#if 1
namespace std 
{
  template<typename T1, typename T2 = int>
    class vector;

  template<typename T1, typename T2> 
    class vector;  
}
#else
namespace __gnu_norm
{
  template<typename T1, typename T2 = int>
    class vector;
}

namespace std
{
  using namespace __gnu_norm __attribute__ ((strong));
}

namespace std 
{
  template<typename T1, typename T2> 
    class vector;  
}
#endif

class Foo { };
typedef std::vector<Foo> FooVec;

-- 
           Summary: namespace association vs. templates part two
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: jason at redhat dot com
        ReportedBy: bkoz at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,larsbj at gullik dot
                    net,rsandifo at redhat dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13594


             reply	other threads:[~2004-01-07  3:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  3:06 bkoz at gcc dot gnu dot org [this message]
2004-01-07  3:15 ` [Bug c++/13594] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-07 17:00 ` aoliva at gcc dot gnu dot org
2004-01-07 19:43 ` aoliva at gcc dot gnu dot org
2004-01-07 21:02 ` aoliva at gcc dot gnu dot org
2004-01-12 16:42 ` bkoz at gcc dot gnu dot org
2004-01-12 18:39 ` aoliva at gcc dot gnu dot org
2004-01-15 14:42 ` cvs-commit at gcc dot gnu dot org
2004-01-15 14:42 ` cvs-commit at gcc dot gnu dot org
2004-01-15 17:44 ` aoliva at gcc dot gnu dot org

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=20040107030635.13594.bkoz@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).