public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 04/18] Remove c_printstr
Date: Wed, 16 Feb 2022 15:46:56 +0000	[thread overview]
Message-ID: <20220216154656.GH2571@redhat.com> (raw)
In-Reply-To: <20220216135518.3162480-5-tom@tromey.com>

* Tom Tromey <tom@tromey.com> [2022-02-16 06:55:04 -0700]:

> This renames c_printstr, removing a layer of indirection.
> ---
>  gdb/c-lang.c    |  8 ++++----
>  gdb/c-lang.h    |  8 --------
>  gdb/language.c  | 12 ------------
>  gdb/rust-lang.c |  5 +++--
>  4 files changed, 7 insertions(+), 26 deletions(-)
> 
> diff --git a/gdb/c-lang.c b/gdb/c-lang.c
> index 342109c94ef..fbbecb696b9 100644
> --- a/gdb/c-lang.c
> +++ b/gdb/c-lang.c
> @@ -190,10 +190,10 @@ language_defn::printchar (int c, struct type *type,
>     characters, or if FORCE_ELLIPSES.  */
>  
>  void
> -c_printstr (struct ui_file *stream, struct type *type, 
> -	    const gdb_byte *string, unsigned int length, 
> -	    const char *user_encoding, int force_ellipses,
> -	    const struct value_print_options *options)
> +language_defn::printstr (struct ui_file *stream, struct type *type, 
> +			 const gdb_byte *string, unsigned int length, 

I know you didn't add them, but there's a trailing whitespace on both
the preceding lines, would you mind fixing these please?

> +			 const char *user_encoding, int force_ellipses,
> +			 const struct value_print_options *options) const
>  {
>    c_string_type str_type;
>    const char *type_encoding;
> diff --git a/gdb/c-lang.h b/gdb/c-lang.h
> index 16c9b116393..5441bfe10c7 100644
> --- a/gdb/c-lang.h
> +++ b/gdb/c-lang.h
> @@ -92,14 +92,6 @@ extern void c_value_print (struct value *, struct ui_file *,
>  
>  extern void c_printchar (int, struct type *, struct ui_file *);
>  
> -extern void c_printstr (struct ui_file * stream,
> -			struct type *elttype,
> -			const gdb_byte *string,
> -			unsigned int length,
> -			const char *user_encoding,
> -			int force_ellipses,
> -			const struct value_print_options *options);
> -
>  extern void c_language_arch_info (struct gdbarch *gdbarch,
>  				  struct language_arch_info *lai);
>  
> diff --git a/gdb/language.c b/gdb/language.c
> index 931abcd3076..20b6d8ccf9b 100644
> --- a/gdb/language.c
> +++ b/gdb/language.c
> @@ -635,18 +635,6 @@ language_defn::value_print_inner
>  
>  /* See language.h.  */
>  
> -void
> -language_defn::printstr (struct ui_file *stream, struct type *elttype,
> -			 const gdb_byte *string, unsigned int length,
> -			 const char *encoding, int force_ellipses,
> -			 const struct value_print_options *options) const
> -{
> -  c_printstr (stream, elttype, string, length, encoding, force_ellipses,
> -	      options);
> -}
> -
> -/* See language.h.  */
> -
>  void
>  language_defn::print_typedef (struct type *type, struct symbol *new_symbol,
>  			      struct ui_file *stream) const
> diff --git a/gdb/rust-lang.c b/gdb/rust-lang.c
> index 7584d2572fa..3668d2d0c6d 100644
> --- a/gdb/rust-lang.c
> +++ b/gdb/rust-lang.c
> @@ -283,8 +283,9 @@ rust_language::printstr (struct ui_file *stream, struct type *type,
>  	{
>  	  /* This is probably some C string, so let's let C deal with
>  	     it.  */
> -	  c_printstr (stream, type, string, length, user_encoding,
> -		      force_ellipses, options);
> +	  this->language_defn::printstr (stream, type, string, length,
> +					 user_encoding, force_ellipses,
> +					 options);

Personally, not a fan of the 'this->' when we're already using the
parent class name.  In ada_language::read_var_value we don't use
'this->'.  But I think it's up to you really, I'm not that offended by
it.

Thanks,
Andrew


  reply	other threads:[~2022-02-16 15:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 13:55 [PATCH 00/18] Refactor character printing Tom Tromey
2022-02-16 13:55 ` [PATCH 01/18] Fix latent quote char bug in generic_printstr Tom Tromey
2022-02-16 15:38   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 02/18] Boolify need_escape in generic_emit_char Tom Tromey
2022-02-16 15:39   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 03/18] Remove c_emit_char Tom Tromey
2022-02-16 15:40   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 04/18] Remove c_printstr Tom Tromey
2022-02-16 15:46   ` Andrew Burgess [this message]
2022-02-16 13:55 ` [PATCH 05/18] Don't use wchar_printable in print_wchar Tom Tromey
2022-02-16 15:52   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 06/18] Fix a latent bug " Tom Tromey
2022-02-16 16:02   ` Andrew Burgess
2022-02-17 22:02     ` Tom Tromey
2022-02-16 13:55 ` [PATCH 07/18] Remove language_defn::emitchar Tom Tromey
2022-02-16 16:12   ` Andrew Burgess
2022-02-17 22:02     ` Tom Tromey
2022-02-16 13:55 ` [PATCH 08/18] Add gdb_iswcntrl Tom Tromey
2022-02-16 16:13   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 09/18] Include \0 in printable wide characters Tom Tromey
2022-02-16 17:19   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 10/18] Use a ui_file in print_wchar Tom Tromey
2022-02-16 17:25   ` Andrew Burgess
2022-02-16 13:55 ` [PATCH 11/18] Add an emitter callback to generic_printstr and generic_emit_char Tom Tromey
2022-02-16 17:47   ` Andrew Burgess
2022-02-16 20:40     ` Tom Tromey
2022-02-16 21:00       ` Tom Tromey
2022-02-16 13:55 ` [PATCH 12/18] Add a default encoding to generic_emit_char and generic_printstr Tom Tromey
2022-02-16 13:55 ` [PATCH 13/18] Change generic_emit_char to print the quotes Tom Tromey
2022-02-16 13:55 ` [PATCH 14/18] Use generic_emit_char in Rust Tom Tromey
2022-02-16 13:55 ` [PATCH 15/18] Use generic_emit_char in Ada Tom Tromey
2022-02-16 13:55 ` [PATCH 16/18] Use generic_emit_char in Modula-2 Tom Tromey
2022-02-16 13:55 ` [PATCH 17/18] Use generic_emit_char in Pascal Tom Tromey
2022-02-16 13:55 ` [PATCH 18/18] Simplify Fortran string printing Tom Tromey

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=20220216154656.GH2571@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).