--- Comment #6 from pinskia at gcc dot gnu dot org 2005-10-09 03:34 ---
The diagnostic problem is where implicit destructor is created. The same
problem occurs with implicit constructor.
This is a dup of bug 20164.
*** This bug has been marked as a duplicate of 20164 ***
--
pinski
--- Comment #5 from pinskia at gcc dot gnu dot org 2005-10-09 03:29 ---
(In reply to comment #4)
> I have to look up what the standard says but I think the standard says that
> exception's deconstructor is nothrow.
The standard says it does have throw() on it. So only thing left is the
--- Comment #4 from pinskia at gcc dot gnu dot org 2005-10-09 03:26 ---
(In reply to comment #3)
> Who do I take the spurious throw spec to? (i.e. where's the bugzilla site for
> glibc++?)
I think that is still a G++ bug. libstdc++ (what you called glibc++) is part of
GCC so here.
I hav
--- Comment #3 from igodard at pacbell dot net 2005-10-09 00:37 ---
OK, I see what is going on now. Here's a simple case:
#include
class syntaxNoError : public std::exception {
std::string message;
};
which gets you:
scanner.cc:2: error: looser throw specifier for `virtua
--- Comment #2 from igodard at pacbell dot net 2005-10-09 00:01 ---
Created an attachment (id=9944)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9944&action=view)
source code (compressed)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24280
--- Comment #1 from igodard at pacbell dot net 2005-10-09 00:00 ---
Created an attachment (id=9943)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9943&action=view)
compiler output
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24280
