From: Tom Tromey <tom@tromey.com>
To: Siva Chandra <sivachandra@google.com>
Cc: Tom Tromey <tom@tromey.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: [PATCH libstdc++ v5] - Add xmethods for std::vector and std::unique_ptr
Date: Thu, 28 Aug 2014 17:15:00 -0000 [thread overview]
Message-ID: <87zjeofsdj.fsf@tromey.com> (raw)
In-Reply-To: <CAGyQ6gy-KmHN2rUaPtMXypxJS3kwKp8-mT_SUELiv0rwWGy0Hg@mail.gmail.com> (Siva Chandra's message of "Thu, 28 Aug 2014 09:33:14 -0700")
>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:
Tom> Yeah, that's my view.
Siva> I am probably not understanding it right again.
It's ok. I am having some trouble myself.
Siva> Are you suggesting that in hook.in, we just have single function
Siva> call like this:
Siva> register_python_hooks (gdb.current_objfile ())
Siva> and, this function register_python_hooks lives somewhere else and
Siva> calls register_libstdcxx_printers and register_libstdcxx_xmethods?
Yeah. I think it's better to put as little as possible in the hook file.
I realize this may sound ridiculous given all the code that is already
there; but that's an artifact of gcc's install-relocatability requirement.
Tom
next prev parent reply other threads:[~2014-08-28 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:39 Siva Chandra
2014-08-27 22:19 ` Jonathan Wakely
2014-08-27 22:38 ` Siva Chandra
2014-08-27 22:58 ` Jonathan Wakely
2014-09-03 18:01 ` Siva Chandra
2014-09-03 22:35 ` Jonathan Wakely
2014-09-03 22:47 ` Siva Chandra
2014-09-04 12:56 ` Siva Chandra
2014-09-10 13:18 ` Jonathan Wakely
2014-09-10 13:44 ` Siva Chandra
2014-08-27 22:31 ` Tom Tromey
2014-08-27 22:36 ` Siva Chandra
2014-08-27 22:46 ` Tom Tromey
2014-08-28 1:51 ` Siva Chandra
2014-08-28 2:11 ` Tom Tromey
2014-08-28 16:33 ` Siva Chandra
2014-08-28 17:15 ` Tom Tromey [this message]
2014-08-28 18:45 ` Siva Chandra
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=87zjeofsdj.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=sivachandra@google.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).