From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/4] Add wrappers for Python implementation functions and methods
Date: Thu, 21 May 2026 15:23:55 -0600 [thread overview]
Message-ID: <877bowjw2c.fsf@tromey.com> (raw)
In-Reply-To: <877bp1cb9f.fsf@redhat.com> (Andrew Burgess's message of "Mon, 18 May 2026 10:33:48 +0100")
>> +noargs_method (std::string_view name, std::string_view doc)
Andrew> Using std::string_view seems a little suspect here.
Yeah. I think some earlier attempt at this required string_view, but
I've changed it to 'const char *' and it's fine.
>> +/* A function that wraps a "repr" or "str" method. */
>> +template<typename C, auto M>
>> +PyObject *
>> +wrap_repr (PyObject *arg)
Andrew> Maybe something like 'wrap_tp_callback' might be better? I just know
Andrew> every time I see 'wrap_repr' for something that isn't 'repr' I'm going
Andrew> to assume copy & paste error, and then have to go and remind myself that
Andrew> 'wrap_repr' has wider uses. Now's a great time to find a better name
Andrew> before this starts getting used more widely..
I changed it to wrap_tp_callback.
Tom
next prev parent reply other threads:[~2026-05-21 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 19:59 [PATCH v2 0/4] Python safety initial work Tom Tromey
2026-05-15 19:59 ` [PATCH v2 1/4] Add gdbpy_borrowed_ref Tom Tromey
2026-05-17 11:40 ` Andrew Burgess
2026-05-21 17:48 ` Tom Tromey
2026-05-21 21:01 ` Tom Tromey
2026-05-15 19:59 ` [PATCH v2 2/4] Add wrappers for some Python APIs Tom Tromey
2026-05-17 12:06 ` Andrew Burgess
2026-05-21 21:05 ` Tom Tromey
2026-05-15 19:59 ` [PATCH v2 3/4] Add wrappers for Python implementation functions and methods Tom Tromey
2026-05-18 9:33 ` Andrew Burgess
2026-05-21 21:23 ` Tom Tromey [this message]
2026-05-18 10:00 ` Andrew Burgess
2026-05-21 22:41 ` Tom Tromey
2026-05-29 15:58 ` Andrew Burgess
2026-05-15 19:59 ` [PATCH v2 4/4] Convert py-tui.c to the "python safety" approach Tom Tromey
2026-05-18 12:39 ` Andrew Burgess
2026-05-21 21:21 ` 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=877bowjw2c.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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