diff options
author | Tom Tromey <tom@tromey.com> | 2023-02-14 09:34:53 -0700 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2023-02-15 15:07:07 -0700 |
commit | b2227e67b4bdee65b1240f725dd2ea214178d984 (patch) | |
tree | 7dbe02ca21d39eb917fcbf74771113914a4e1fd6 /gdb/value.c | |
parent | 141cd158423a5ee248245fb2075fd2e5a580cff2 (diff) | |
download | fsf-binutils-gdb-b2227e67b4bdee65b1240f725dd2ea214178d984.zip fsf-binutils-gdb-b2227e67b4bdee65b1240f725dd2ea214178d984.tar.gz fsf-binutils-gdb-b2227e67b4bdee65b1240f725dd2ea214178d984.tar.bz2 |
Change value::m_modifiable to bool
This changes value::m_modifiable to be a bool and updates the various
uses.
Reviewed-By: Bruno Larsen <blarsen@redhat.com>
Diffstat (limited to 'gdb/value.c')
-rw-r--r-- | gdb/value.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/value.c b/gdb/value.c index 34a282b..2dc2dab 100644 --- a/gdb/value.c +++ b/gdb/value.c @@ -1677,7 +1677,7 @@ value::record_latest () /* We preserve VALUE_LVAL so that the user can find out where it was fetched from. This is a bit dubious, because then *&$1 does not just return $1 but the current contents of that location. c'est la vie... */ - set_modifiable (0); + set_modifiable (false); value_history.push_back (release_value (this)); @@ -2174,7 +2174,7 @@ set_internalvar (struct internalvar *var, struct value *val) default: new_kind = INTERNALVAR_VALUE; struct value *copy = val->copy (); - copy->set_modifiable (1); + copy->set_modifiable (true); /* Force the value to be fetched from the target now, to avoid problems later when this internalvar is referenced and the target is gone or @@ -2498,7 +2498,7 @@ value::from_xmethod (xmethod_worker_up &&worker) v = value::allocate (builtin_type (target_gdbarch ())->xmethod); v->m_lval = lval_xcallable; v->m_location.xm_worker = worker.release (); - v->m_modifiable = 0; + v->m_modifiable = false; return v; } |