This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: g++ 2.95 typeinfo::name()
- To: Mike Stump <mrs at windriver dot com>
- Subject: Re: g++ 2.95 typeinfo::name()
- From: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>
- Date: Mon, 22 Jan 2001 19:53:29 +0100
- Cc: aoliva at redhat dot com, rssh at gvinpin dot grad dot kiev dot ua, Oliver dot Kellogg at vs dot dasa dot de, gcc at gcc dot gnu dot org
mrs@windriver.com said:
>> >> Yep. It would also be correct if it just returned an empty string
>> for
>> >> all types.
>> > No. must be true:
>> > typeof(x)==typeof(y) <=> typeof(x).name equal typeof(y).name()
>> Nope. All the standard says is that the result of type_info::name()
>> is an implementation-defined null-terminated byte string.
> The standard is irrelevant in this case. What Oliver said must be
> true, must be true, really. Just meeting the standard is fine in many
> cases, however, at times, we do want to do more than the standard.
Well, I interpreted that in a different way. name() can always be an
empty string but different types get different empty strings so that
the pointers are not equal. Everything lies in the type of equality
used !! Thus, my belief is that Alexandre is totally right...
--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
--------------------------------------------------------------------
PGP signature