Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Partial infcmd.c cleanup
Date: Mon, 26 Jan 2004 06:18:00 -0000	[thread overview]
Message-ID: <ubror2pwa.fsf@elta.co.il> (raw)
In-Reply-To: <200401251732.i0PHWmRq007000@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sun, 25 Jan 2004 18:32:48 +0100 (CET))

> Date: Sun, 25 Jan 2004 18:32:48 +0100 (CET)
> From: Mark Kettenis <kettenis@chello.nl>
> 
> Since I'll be changing this bit of code I though I'd give it a cleanup
> first.  Mostly wrapping long lines and adding some missing whitespace.
> 
> Committed as obvious,

I think changing finish_command_continuation from a void function into
a static void function does not really qualify as obvious.  I'm
talking about this part of the patch:

>  /* Stuff that needs to be done by the finish command after the target
> -   has stopped.  In asynchronous mode, we wait for the target to stop in
> -   the call to poll or select in the event loop, so it is impossible to
> -   do all the stuff as part of the finish_command function itself. The
> -   only chance we have to complete this command is in
> -   fetch_inferior_event, which is called by the event loop as soon as it
> -   detects that the target has stopped. This function is called via the
> -   cmd_continuation pointer. */
> -void
> +   has stopped.  In asynchronous mode, we wait for the target to stop
> +   in the call to poll or select in the event loop, so it is
> +   impossible to do all the stuff as part of the finish_command
> +   function itself.  The only chance we have to complete this command
> +   is in fetch_inferior_event, which is called by the event loop as
> +   soon as it detects that the target has stopped. This function is
> +   called via the cmd_continuation pointer.  */
> +
> +static void
>  finish_command_continuation (struct continuation_arg *arg)

Not that I'm objected to this change, but IMHO it shouldn't have been
done without at least a call for comments, or a few days of delay, to
give people some time to react.


  reply	other threads:[~2004-01-26  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 17:32 Mark Kettenis
2004-01-26  6:18 ` Eli Zaretskii [this message]
2004-01-26 11:55   ` Mark Kettenis
2004-01-26 16:55     ` Andrew Cagney

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=ubror2pwa.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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