This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: g++ 2.95 typeinfo::name()
- To: <rssh at gvinpin dot grad dot kiev dot ua>
- Subject: Re: g++ 2.95 typeinfo::name()
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 22 Jan 2001 10:58:25 -0200
- Cc: "Kellogg, Oliver" <Oliver dot Kellogg at vs dot dasa dot de>, "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Organization: GCC Team, Red Hat
- References: <Pine.LNX.4.04.10101221410580.21707-100000@gvinpin.grad.kiev.ua>
On Jan 22, 2001, <rssh@gvinpin.grad.kiev.ua> wrote:
> On 22 Jan 2001, Alexandre Oliva wrote:
>> 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.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me