Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Luis Machado <lgustavo@codesourcery.com>,
	Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] Change return type of ui_out redirect to void
Date: Tue, 10 Jan 2017 16:33:00 -0000	[thread overview]
Message-ID: <48d83f3b03e18eff0d1c55c77361da04@polymtl.ca> (raw)
In-Reply-To: <d074a351-0dbe-caf5-f17d-c17d1f0e1158@redhat.com>

On 2017-01-10 10:50, Pedro Alves wrote:
> On 01/03/2017 04:17 PM, Simon Marchi wrote:
> 
>> 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!
> 
> OK with that change.
> 
> BTW, also spotted a spurious whitespace after "*" here:
> 
>  > @@ -163,7 +163,7 @@ class ui_out
>  >      ATTRIBUTE_PRINTF (2,0) = 0;
>  >    virtual void do_wrap_hint (const char *identstring) = 0;
>  >    virtual void do_flush () = 0;
>  > -  virtual int do_redirect (struct ui_file * outstream) = 0;
>  > +  virtual void do_redirect (struct ui_file * outstream) = 0;
> 
> Thanks,
> Pedro Alves

Oh, right, same in cli-out.h and mi-out.h.  I fixed them all and pushed, 
thanks.


      reply	other threads:[~2017-01-10 16:33 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
2017-01-10 15:50     ` Pedro Alves
2017-01-10 16:33       ` Simon Marchi [this message]

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=48d83f3b03e18eff0d1c55c77361da04@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.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