From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: [URGENT] Ideas for Google Summer of Code
Date: Fri, 21 Feb 2014 18:54:00 -0000 [thread overview]
Message-ID: <m38ut4pa8m.fsf@redhat.com> (raw)
In-Reply-To: <5307239F.1000509@redhat.com> (Pedro Alves's message of "Fri, 21 Feb 2014 09:59:59 +0000")
On Friday, February 21 2014, Pedro Alves wrote:
> I'm too late now, one thought just crossed my mind: it's kind of
> odd that GDB has all this pretty printing machinery in place, but doesn't
> have pretty printers for its own structures, like struct type/main_type,
> and VECs. :-P It'd be nice to address that. :-)
You're not late! We're allowed to edit/extend the page after the
deadline, there's no problem :-). I will add this idea as well, thanks!
--
Sergio
prev parent reply other threads:[~2014-02-21 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 19:12 Sergio Durigan Junior
2014-02-20 7:31 ` Joel Brobecker
2014-02-20 13:48 ` Sergio Durigan Junior
2014-02-21 9:55 ` Pedro Alves
2014-02-21 18:53 ` Sergio Durigan Junior
2014-02-21 10:57 ` Pedro Alves
2014-02-21 18:24 ` Tom Tromey
2014-02-21 19:00 ` Jan Kratochvil
2014-02-21 18:54 ` Sergio Durigan Junior [this message]
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=m38ut4pa8m.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb@sourceware.org \
--cc=palves@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