This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC 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: Wed, 27 Aug 2014 18:51:02 -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>
On Wed, Aug 27, 2014 at 3:45 PM, Tom Tromey <tom@tromey.com> wrote:
> Siva> I misunderstood then. But, I still do not understand what you mean by
> Siva> "single function".
>
> I re-read my original note, and I think I wasn't very clear. Sorry
> about that.
>
> All I mean here is that I think it's better to have a single
> registration function in the libstdc++ python code. This function can
> do all the needed work.
My patch is still using a single function to register libstdc++
xmethods. Do you mean there should be a single function for pretty
printers and xmethods together?
Thanks,
Siva Chandra