aboutsummaryrefslogtreecommitdiff
path: root/gdb/value.h
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2020-12-13 09:51:42 -0700
committerTom Tromey <tom@tromey.com>2020-12-13 09:51:42 -0700
commitf5756acc153e2605a0468b461ff4f6b0942a68b7 (patch)
tree8b5bcb0dedcceabcf0fb774201e3acfa7a29aee2 /gdb/value.h
parent862fcbd8f02b03cbf37b452e35bff8361d7a0208 (diff)
downloadbinutils-f5756acc153e2605a0468b461ff4f6b0942a68b7.zip
binutils-f5756acc153e2605a0468b461ff4f6b0942a68b7.tar.gz
binutils-f5756acc153e2605a0468b461ff4f6b0942a68b7.tar.bz2
Constify parse_and_eval_type
I noticed that the argumen to parse_and_eval_type could be "const". This patch implements this change. I wonder if this could be removed. It's only called via check_stub_method_group, which seems questionable to me. However, I didn't look into doing this. gdb/ChangeLog 2020-12-13 Tom Tromey <tom@tromey.com> * gdbtypes.c (safe_parse_type): Make argument const. * value.h (parse_and_eval_type): Make argument const. * eval.c (parse_and_eval_type): Make argument const.
Diffstat (limited to 'gdb/value.h')
-rw-r--r--gdb/value.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/value.h b/gdb/value.h
index d026c8e..25937f3 100644
--- a/gdb/value.h
+++ b/gdb/value.h
@@ -939,7 +939,7 @@ extern struct value *parse_and_eval (const char *exp);
extern struct value *parse_to_comma_and_eval (const char **expp);
-extern struct type *parse_and_eval_type (char *p, int length);
+extern struct type *parse_and_eval_type (const char *p, int length);
extern CORE_ADDR parse_and_eval_address (const char *exp);