From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 1/4] Use scoped_restore in a couple of interp-related places
Date: Fri, 25 May 2018 18:06:00 -0000 [thread overview]
Message-ID: <a7accbe8-055f-a069-939a-dcbbebb212b9@redhat.com> (raw)
In-Reply-To: <20180430051207.19979-2-tom@tromey.com>
On 04/30/2018 06:12 AM, Tom Tromey wrote:
> While looking through the "interp" code I found a couple of spots that
> could use scoped_restore.
>
> ChangeLog
> 2018-04-29 Tom Tromey <tom@tromey.com>
>
> * cli/cli-interp.c (safe_execute_command): Ues scoped_restore.
Typo: "Ues" -> "Use".
> @@ -372,9 +371,6 @@ safe_execute_command (struct ui_out *command_uiout, const char *command,
> }
> END_CATCH
>
> - /* Restore the global builder. */
> - current_uiout = saved_uiout;
> -
I was a little worried about whether exception_print could use current_uiout,
but it seems not. So OK.
> /* FIXME: cagney/2005-01-13: This shouldn't be needed. Instead the
> caller should print the exception. */
> exception_print (gdb_stderr, e);
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-05-25 17:58 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 [this message]
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
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=a7accbe8-055f-a069-939a-dcbbebb212b9@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