This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/11685] typeinfo is not demangled in error messages


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From gdr at integrable-solutions dot net  2003-08-29 19:36 -------
Subject: Re:  typeinfo is not demangled in error messages

"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| Gaby, there might be a simpler way: the message reads 
|   `get_uuidof(const std::type_info&)((&_ZTIi))' 
| i.e. function_name(type of argument)((value of argument)). If we
| just omit the value of the argument, then this would already be
| enough. I find the format quite confusing anyway. 

I agree on the confusing looking of the message.
However, we cannot omit the argument because it is the value of the
function that is being used.  What we can avoid, however, is getting
the mangled name.  I believe this is just another case of the
front-end being too eager.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]