From 62a49610b840edcddb0cc38d1f2559f627ea0c08 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Fri, 21 Sep 2012 17:33:17 +0000 Subject: [PATCH] * c-typeprint.c (cp_type_print_derivation_info): Fix comment. --- gdb/ChangeLog | 4 ++++ gdb/c-typeprint.c | 7 +------ 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index ae08dd46f9b..fdbea6f4067 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2012-09-21 Tom Tromey + + * c-typeprint.c (cp_type_print_derivation_info): Fix comment. + 2012-09-21 Andrew Burgess * findvar.c (read_frame_register_value): Mark the result value as diff --git a/gdb/c-typeprint.c b/gdb/c-typeprint.c index 92bc47d0f91..71d84cffbef 100644 --- a/gdb/c-typeprint.c +++ b/gdb/c-typeprint.c @@ -131,12 +131,7 @@ c_print_typedef (struct type *type, } In general, gdb should try to print the types as closely as - possible to the form that they appear in the source code. - - Note that in case of protected derivation gcc will not say - 'protected' but 'private'. The HP's aCC compiler emits specific - information for derivation via protected inheritance, so gdb can - print it out */ + possible to the form that they appear in the source code. */ static void cp_type_print_derivation_info (struct ui_file *stream, -- 2.30.2