This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH libstdc++ v5] - Add xmethods for std::vector and std::unique_ptr
- From: Siva Chandra <sivachandra at google dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, "libstdc++" <libstdc++ at gcc dot gnu dot org>, Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Date: Thu, 28 Aug 2014 09:33:14 -0700
- Subject: Re: [PATCH libstdc++ v5] - Add xmethods for std::vector and std::unique_ptr
- Authentication-results: sourceware.org; auth=none
- References: <CAGyQ6gxAYwoi3gLkH-Ut_qRfHpTbV0Dke+bd9BRk_e7cWj4nOA at mail dot gmail dot com> <87y4u95zv9 dot fsf at tromey dot com> <CAGyQ6gzTNQvpiqC_Jzt_kkAUeCH34pA5FF8m-_w-RWJ5w1YutQ at mail dot gmail dot com> <87tx4x5z6u dot fsf at tromey dot com> <CAGyQ6gxDzDAs6L59ggh70n_OPWBDOoMubtOKjHP1Y6OCMdc2Mg at mail dot gmail dot com> <87ha0x5pnq dot fsf at tromey dot com>
On Wed, Aug 27, 2014 at 7:11 PM, Tom Tromey <tom@tromey.com> wrote:
> Siva> My patch is still using a single function to register libstdc++
> Siva> xmethods. Do you mean there should be a single function for pretty
> Siva> printers and xmethods together?
>
> Yeah, that's my view.
I am probably not understanding it right again. Are you suggesting
that in hook.in, we just have single function call like this:
register_python_hooks (gdb.current_objfile ())
and, this function register_python_hooks lives somewhere else and
calls register_libstdcxx_printers and register_libstdcxx_xmethods?
Thanks,
Siva Chandra