From: Tom Tromey <tromey@redhat.com>
To: Dragos Tatulea <dragos.tatulea@gmail.com>
Cc: keiths@redhat.com, archer@sourceware.org,
jan.kratochvil@redhat.com, cmoller@redhat.com
Subject: Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01
Date: Fri, 25 Sep 2009 20:45:00 -0000 [thread overview]
Message-ID: <m3iqf6wy7a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <6d1764b50909251238i6471fcacreea5cfbab57cdd2d@mail.gmail.com> (Dragos Tatulea's message of "Fri, 25 Sep 2009 22:38:41 +0300")
>>>>> "Dragos" == Dragos Tatulea <dragos.tatulea@gmail.com> writes:
Tom> This seems like a generic bug, though. So, it could be fixed either
Tom> separately or at the same time the default is flipped.
Dragos> Why is this a bug? Isn't objectprint supposed to follow up to
Dragos> the original/true type?
I see what you mean.
But, it seems like it would be a little more user-friendly to print the
original type name if we examine the runtime type and find that it is
identical to the declared type (after typdef stripping).
Dragos> Maybe it's not such a good idea to show up in mid struct. Maybe
Dragos> display the usual output and then print warnings on following
Dragos> lines. Dunno' if it's actually possible (noob alert!).
Probably not easily, but I'm sure it could be managed.
But, when printing a long structure this is likely to be more confusing.
Tom
next prev parent reply other threads:[~2009-09-25 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 14:08 Dragos Tatulea
2009-09-25 18:40 ` Tom Tromey
2009-09-25 19:39 ` Dragos Tatulea
2009-09-25 20:45 ` Tom Tromey [this message]
2009-09-27 12:22 ` set print objct pros/cons [Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01] Jan Kratochvil
2009-09-27 17:14 ` Keith Seitz
2009-09-27 18:26 ` Jan Kratochvil
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 19:44 [Keith Seitz] Re: [tools-team] Status 2008-09-01 Tom Tromey
2009-09-02 21:44 ` Jan Kratochvil
2009-09-03 19:19 ` Tom Tromey
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=m3iqf6wy7a.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=cmoller@redhat.com \
--cc=dragos.tatulea@gmail.com \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.com \
/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).