From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [RFA 0/4] add ref_ptr::new_reference
Date: Mon, 30 Apr 2018 04:21:00 -0000 [thread overview]
Message-ID: <20180430042147.28337-1-tom@tromey.com> (raw)
This patch introduces a new ref_ptr::new_reference convenience
function and then changes various places in gdb to use it. This
consolidates some existing boilerplate into a simpler idiom.
Regression tested by the buildbot.
Tom
next reply other threads:[~2018-04-30 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 4:21 Tom Tromey [this message]
2018-04-30 4:21 ` [RFA 1/4] Introduce ref_ptr::new_reference Tom Tromey
2018-04-30 4:21 ` [RFA 3/4] Use new_reference for struct value Tom Tromey
2018-04-30 17:05 ` Pedro Alves
2018-04-30 17:32 ` Tom Tromey
2018-04-30 4:21 ` [RFA 2/4] Remove new_bfd_ref Tom Tromey
2018-04-30 4:21 ` [RFA 4/4] Change Python code to use new_reference Tom Tromey
2018-04-30 13:34 ` Phil Muldoon
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=20180430042147.28337-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