public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38764]  New: bogus 'changes meaning' error?
Date: Thu, 08 Jan 2009 12:22:00 -0000	[thread overview]
Message-ID: <bug-38764-7667@http.gcc.gnu.org/bugzilla/> (raw)

following code snipet is reducted testcase from external application.
g++ and comeau online accept/reject source differently.

template < class T >
struct A
{
};
template < class U >
struct B
{
#if 1
        typedef A< float > A; // <-- accepted by comeau but...
        // g++: error: declaration of typedef struct A<float> B<U>::A
        // g++: error: changes meaning of A from struct A<float>
#else
        typedef ::A< float > A; // <-- accepted by g++ but...
        // comeau: class member typedef may not be redeclared
        //         typedef ::A< float > A;
        //                              ^
#endif
};


-- 
           Summary: bogus 'changes meaning' error?
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pluto at agmk dot net


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


             reply	other threads:[~2009-01-08 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 12:22 pluto at agmk dot net [this message]
2009-01-08 12:50 ` [Bug c++/38764] " rguenth at gcc dot gnu dot org
2009-01-08 12:56 ` pluto at agmk dot net
2009-01-08 19:16 ` pinskia at gmail dot com
2009-01-08 19:16 ` [Bug c++/38764] New: " Andrew Thomas Pinski
2009-01-09 19:39 ` [Bug c++/38764] " pluto at agmk dot net

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=bug-38764-7667@http.gcc.gnu.org/bugzilla/ \
    --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).