From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Convert valpy_call to the "python safety" approach
Date: Mon, 10 Aug 2026 11:53:52 +0200 [thread overview]
Message-ID: <379ec062-44c0-488a-8ff9-87fe235c4b6d@suse.de> (raw)
In-Reply-To: <20260809075952.3244926-1-tdevries@suse.de>
On 8/9/26 9:59 AM, Tom de Vries wrote:
> I added a wrap_tp_call template to enforce and handle the new prototype of
> valpy_call:
> ...
> - valpy_call, /*tp_call*/
> + wrap_tp_call<valpy_call>, /*tp_call*/
> ...
>
I realized that by making valpy_call a method of struct value_object, I
could use varargs_wrapper instead. I'll send a v2 shortly.
Thanks,
- Tom
prev parent reply other threads:[~2026-08-10 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 7:59 Tom de Vries
2026-08-10 9:53 ` Tom de Vries [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=379ec062-44c0-488a-8ff9-87fe235c4b6d@suse.de \
--to=tdevries@suse.de \
--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