From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Change return type of ui_out redirect to void
Date: Tue, 03 Jan 2017 16:17:00 -0000 [thread overview]
Message-ID: <4270f5e03af2b1e554fc4ddaf1a0a8c7@polymtl.ca> (raw)
In-Reply-To: <81609b60-0821-3f1b-7613-5bf691727d5f@codesourcery.com>
On 2016-12-23 14:44, Luis Machado wrote:
> On 12/22/2016 04:07 PM, Simon Marchi wrote:
>> diff --git a/gdb/cli/cli-logging.c b/gdb/cli/cli-logging.c
>> index 46c23064fc..02e2705310 100644
>> --- a/gdb/cli/cli-logging.c
>> +++ b/gdb/cli/cli-logging.c
>> @@ -130,13 +130,11 @@ set_logging_redirect (char *args, int from_tty,
>> struct cmd_list_element *c)
>>
>> /* There is a former output pushed on the ui_out_redirect stack.
>> We
>> want to replace it by OUTPUT so we must pop the former value
>> - first. We should either do both the pop and push or to do
>> - neither of it. At least do not try to push OUTPUT if the pop
>> - already failed. */
>> + first. Ideally, we should either do both the pop and push or to
>> do
>> + neither of it. */
>
> This comment reads funny. Maybe we should fix it while at it.
>
> "... we should either do both the pop and push or do neither of them.
> "?
Right, now that I re-read it, it does sound funny. Fixed locally to:
/* There is a former output pushed on the ui_out_redirect stack. We
want to replace it by OUTPUT so we must pop the former value
- first. We should either do both the pop and push or to do
- neither of it. At least do not try to push OUTPUT if the pop
- already failed. */
+ first. Ideally, we should either do both the pop and push or do
+ neither of them. */
Thanks!
next prev parent reply other threads:[~2017-01-03 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 22:08 Simon Marchi
2016-12-23 19:44 ` Luis Machado
2017-01-03 16:17 ` Simon Marchi [this message]
2017-01-10 15:50 ` Pedro Alves
2017-01-10 16:33 ` Simon Marchi
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=4270f5e03af2b1e554fc4ddaf1a0a8c7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=simon.marchi@ericsson.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