Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 4/4] Remove interp_name
Date: Fri, 25 May 2018 18:41:00 -0000	[thread overview]
Message-ID: <0b5df1d7-ea68-8bb0-bbdf-6a370b35042c@redhat.com> (raw)
In-Reply-To: <20180430051207.19979-5-tom@tromey.com>

On 04/30/2018 06:12 AM, Tom Tromey wrote:
> This removes the interp_name function.  It is only used a few spots --
> one of which was only calling it on "this".  It's simpler to remove
> it; and should class interp become opaque in the future, it will be
> just as easy to update the two remaining spots to use an accessor.

Yeah, IIRC, it used to be opaque until I C++ified it.  Not seeing
a need to go back.

> 
> ChangeLog
> 2018-04-29  Tom Tromey  <tom@tromey.com>
> 
> 	* interps.c (interp_name): Remove.
> 	* mi/mi-interp.c (mi_interp::init): Update.
> 	* interps.h (interp_name): Remove.
> 	(~scoped_restore_interp): Update.
> 	* tui/tui.c (tui_enable): Update.

> diff --git a/gdb/tui/tui.c b/gdb/tui/tui.c
> index 7943a61676..9e2520b4fc 100644
> --- a/gdb/tui/tui.c
> +++ b/gdb/tui/tui.c
> @@ -415,7 +415,7 @@ tui_enable (void)
>  
>        /* If the top level interpreter is not the console/tui (e.g.,
>  	 MI), enabling curses will certainly lose.  */
> -      interp = interp_name (top_level_interpreter ());
> +      interp = top_level_interpreter ()->name;
>        if (strcmp (interp, INTERP_TUI) != 0)
>  	error (_("Cannot enable the TUI when the interpreter is '%s'"), interp);

Not sure.  The name is supposedly read-only, which would
suggest renaming the field to m_name and adding a name()
getter.  WDYT?

Thanks,
Pedro Alves


  reply	other threads:[~2018-05-25 18:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30  5:12 [RFA 0/4] minor interp-related cleanups Tom Tromey
2018-04-30  5:12 ` [RFA 1/4] Use scoped_restore in a couple of interp-related places Tom Tromey
2018-05-25 18:06   ` Pedro Alves
2018-04-30  5:12 ` [RFA 2/4] Change the as_*_interp functions to use dynamic_cast Tom Tromey
2018-05-25 18:12   ` Pedro Alves
2018-04-30  5:12 ` [RFA 3/4] Remove interp_ui_out Tom Tromey
2018-05-25 18:37   ` Pedro Alves
2018-04-30  5:12 ` [RFA 4/4] Remove interp_name Tom Tromey
2018-05-25 18:41   ` Pedro Alves [this message]
2018-05-25 18:47     ` Tom Tromey
2018-05-25 19:36       ` Pedro Alves
2018-05-25 17:34 ` [RFA 0/4] minor interp-related cleanups 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=0b5df1d7-ea68-8bb0-bbdf-6a370b35042c@redhat.com \
    --to=palves@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