This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: g++ 2.95 typeinfo::name()
- To: aoliva at redhat dot com, rssh at gvinpin dot grad dot kiev dot ua
- Subject: Re: g++ 2.95 typeinfo::name()
- From: Mike Stump <mrs at windriver dot com>
- Date: Mon, 22 Jan 2001 10:31:08 -0800 (PST)
- Cc: Oliver dot Kellogg at vs dot dasa dot de, gcc at gcc dot gnu dot org
> To: <rssh@gvinpin.grad.kiev.ua>
> Cc: "Kellogg, Oliver" <Oliver.Kellogg@vs.dasa.de>,
> "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
> From: Alexandre Oliva <aoliva@redhat.com>
> Date: 22 Jan 2001 10:58:25 -0200
> 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.
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.