From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Use gdbpy_ref more in gdb/python
Date: Sun, 28 Oct 2018 18:13:00 -0000 [thread overview]
Message-ID: <20181028181337.21681-1-tom@tromey.com> (raw)
This changes a few more spots in the Python layer to return a
gdbpy_ref. This is a small improvement because it makes the reference
ownership part of the type system rather than merely a convention.
Regression tested by the buildbot.
Tom
next reply other threads:[~2018-10-28 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 18:13 Tom Tromey [this message]
2018-10-28 18:13 ` [PATCH 1/3] Return gdbpy_ref from gdb_py_object_from_*longest Tom Tromey
2018-10-28 18:13 ` [PATCH 3/3] Return gdbpy_ref from gdbpy_get_varobj_pretty_printer Tom Tromey
2018-10-28 18:13 ` [PATCH 2/3] Return gdbpy_ref from some Python string functions Tom Tromey
2018-11-04 15:01 ` [PATCH 0/3] Use gdbpy_ref more in gdb/python 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=20181028181337.21681-1-tom@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).