This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why does debugging "pure virtual method called" have to be sohard?
- To: rich_paul at bigfoot dot com
- Subject: Re: Why does debugging "pure virtual method called" have to be sohard?
- From: Martin von Loewis <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Mon, 2 Nov 1998 14:12:38 +0100
- CC: egcs at cygnus dot com
- References: <Pine.LNX.4.05.9811011738000.23891-100000@dt021n1a.tampabay.rr.com>
Paul,
Thanks for your patch. I personally like it; however, I'm not the one
deciding on it.
Some comments, though:
- I'm not sure how good it is to put this into exception.cc. People
often complain that they have to link things they didn't
buy. Allowing fine-grained linkage of the runtime is a must, IMHO.
- You are indeed free to use the double-underscore. Any such name is
reserved. In addition, any name starting with an underscore and
followed by an uppercase letter is reserved. Furthermore, any name
starting with an underscore is reserved in the global namespace and
in ::std.
- __pure_virtual absolutely must have "C" linkage, unless you want to
break compatibility with existing libraries. Not having any
decorations in the assembler output is the defining property of "C"
linkage. You can put extern "C" functions into namespaces.
- I agree that a new namespace might be a good idea, like __gnu.
__g++, of course, is not a valid identifier.
Regards,
Martin