diff options
author | Tom Tromey <tom@tromey.com> | 2018-04-29 20:59:21 -0600 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2018-04-30 11:33:11 -0600 |
commit | 7c1b5f3db73d7ecab03dc4e866e291582935fb04 (patch) | |
tree | 01ac632a9ca2a8de49aba34932ec8d7c14ca57b8 /gdb/inferior.c | |
parent | Remove long_long_align_bit gdbarch attribute (diff) | |
download | binutils-gdb-7c1b5f3db73d7ecab03dc4e866e291582935fb04.tar.gz binutils-gdb-7c1b5f3db73d7ecab03dc4e866e291582935fb04.tar.bz2 binutils-gdb-7c1b5f3db73d7ecab03dc4e866e291582935fb04.zip |
Introduce ref_ptr::new_reference
I noticed a common pattern with gdb::ref_ptr, where callers would
"incref" and then create a new wrapper object, like:
Py_INCREF (obj);
gdbpy_ref<> ref (obj);
The ref_ptr constructor intentionally does not acquire a new
reference, but it seemed to me that it would be reasonable to add a
static member function that does so.
In this patch I chose to call the function "new_reference". I
considered "acquire_reference" as well, but "new" seemed less
ambiguous than "acquire" to me.
ChangeLog
2018-04-30 Tom Tromey <tom@tromey.com>
* common/gdb_ref_ptr.h (ref_ptr::new_reference): New static
method.
Diffstat (limited to 'gdb/inferior.c')
0 files changed, 0 insertions, 0 deletions