From: kunert@physik.tu-dresden.de
To: <oliva@dcc.unicamp.br>
Cc: <egcs@cygnus.com>
Subject: Re: type_info::name question
Date: Fri, 09 Oct 1998 03:40:00 -0000 [thread overview]
Message-ID: <9810039073.AA907398810@mrbusy.demon.co.uk> (raw)
Alexandre Oliva wrote:
>
> Thomas Kunert <kunert@physik.tu-dresden.de> writes:
>
> > IMHO, type_info::name isn't useful at all if it returns some cryptic
> > string.
>
> type_info::name *isn't* useful at all, as defined in the standard.
Only if one clings to the paper as you do.
The function is called `name', not `some_arbitrary_string'. IMO, that is
description enough.
``Implementation defined'' doesn't mean ``as unuseful as possible to
prevent portability problems'' but ``make the best of it, everybody
should know about portability''. And if the function does what it's name
suggests -- giving the name of the type in some readable language -- it
*is* useful.
> If you really want a readable representation,
> I've already explained that it's just a matter of running c++filt or
> embedding it into your application.
Of course I can do that, in fact I have done this a long time ago, to
port some perfectly working code to egcs, but I hate rewriting functions
from the standard library only because of some weird chosen
implementation defined values.
Regards,
Thomas
next reply other threads:[~1998-10-09 3:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-09 3:40 kunert [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-10-12 20:53 Mike Stump
1998-10-13 19:22 ` Mark Mitchell
[not found] <9810039073.AA907398810.cygnus.egcs@mrbusy.demon.co.uk>
1998-10-11 13:16 ` Jason Merrill
1998-10-11 19:05 ` H.J. Lu
[not found] ` <u9ogrij1s9.fsf.cygnus.egcs@yorick.cygnus.com>
1998-10-12 22:24 ` Nathan Myers
1998-09-22 5:33 Ryszard Kabatek
1998-09-14 2:45 Ryszard Kabatek
1998-09-14 5:49 ` Alexandre Oliva
1998-09-16 1:48 ` Thomas Kunert
1998-09-16 21:52 ` Alexandre Oliva
1998-09-21 3:54 ` Thomas Kunert
1998-09-21 7:32 ` Alexandre Oliva
1998-09-21 9:44 ` Thomas Kunert
1998-09-22 6:35 ` Martin von Loewis
1998-09-17 9:59 ` Martin von Loewis
1998-09-14 11:02 ` Todd Vierling
[not found] ` <35FF61BF.301D5EC7.cygnus.egcs@physik.tu-dresden.de>
1998-09-16 21:52 ` Nathan Myers
1998-09-17 18:37 ` Martin von Loewis
[not found] ` <199809172030.WAA01914.cygnus.egcs@mira.isdn.cs.tu-berlin.de>
1998-09-18 22:10 ` Nathan Myers
1998-09-19 12:03 ` Martin von Loewis
[not found] ` <199809191751.TAA00242.cygnus.egcs@mira.isdn.cs.tu-berlin.de>
1998-09-19 19:00 ` Nathan Myers
1998-09-21 14:55 ` Jason Merrill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9810039073.AA907398810@mrbusy.demon.co.uk \
--to=kunert@physik.tu-dresden.de \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).