public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/25552]  New: [4.0/4.1/4.2 regression] Invalid destructor name accepted in friend declaration
@ 2005-12-23 22:49 reichelt at gcc dot gnu dot org
  2005-12-23 22:50 ` [Bug c++/25552] " reichelt at gcc dot gnu dot org
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: reichelt at gcc dot gnu dot org @ 2005-12-23 22:49 UTC (permalink / raw)
  To: gcc-bugs

The following invalid code snippet is not rejected:

====================
struct A {};

struct B
{
  friend A::~B();
};
====================

The problem appeared in gcc 4.0.0.


-- 
           Summary: [4.0/4.1/4.2 regression] Invalid destructor name
                    accepted in friend declaration
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: accepts-invalid, monitored, patch
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: reichelt at gcc dot gnu dot org
        ReportedBy: reichelt at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2006-01-24 22:00 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-12-23 22:49 [Bug c++/25552] New: [4.0/4.1/4.2 regression] Invalid destructor name accepted in friend declaration reichelt at gcc dot gnu dot org
2005-12-23 22:50 ` [Bug c++/25552] " reichelt at gcc dot gnu dot org
2006-01-04 13:53 ` reichelt at gcc dot gnu dot org
2006-01-15 22:20 ` mmitchel at gcc dot gnu dot org
2006-01-24 11:56 ` reichelt at gcc dot gnu dot org
2006-01-24 11:58 ` [Bug c++/25552] [4.0/4.1 " reichelt at gcc dot gnu dot org
2006-01-24 21:39 ` reichelt at gcc dot gnu dot org
2006-01-24 21:45 ` reichelt at gcc dot gnu dot org
2006-01-24 22:00 ` [Bug c++/25552] [4.0/4.1/4.2 " reichelt at gcc dot gnu dot org

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).