From: Andrew Cagney <ac131313@cygnus.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] remote debugging patches
Date: Mon, 11 Mar 2002 07:53:00 -0000 [thread overview]
Message-ID: <3C8CD30A.8070207@cygnus.com> (raw)
In-Reply-To: <3C8CC863.8030206@suse.cz>
> Andrew Cagney wrote:
> Yes fine, er almost. Can you change the name of this to ``DONT_WAIT_FOREVER_FLAG'' and suggest making it an enum. (so GDB can print it :-)
>
> Why DONT_WAIT_FOREWER? IMHO wait_forewer is correct, because 0 means don't wait forewer (the default) and 1 means yes, wait forever.
But you defined:
> +#define WAIT_FOREVER_FLAG 0
Anyway, I think I misunderstood the reason for the change:
> The first one is pretty straightforward and just makes use of the last parameter to getpkt().
As far as I can tell, you've just replaced the last parameter of
getpkt() with a hardwired value - initially a macro but now an enum. Is
that the intent?
When I wrote:
> If you're feeling really inspired (...), you could even introduce an enum to handle both the DO and DONT cases.
I was thinking of something more like:
enum { do_wait_forever, dont_wait_forever } wait_forever_flag;
int
getpkt (..., enum wait_forever_flag forever, ...)
{
if (forever == do_wait_forever)
...
else
...
et.al.
}
{
getpkt (blah, dont_wait_forever);
}
Andrew
next prev parent reply other threads:[~2002-03-11 15:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 10:34 Michal Ludvig
2002-03-10 11:35 ` Daniel Jacobowitz
2002-03-10 11:43 ` Michal Ludvig
2002-03-10 14:30 ` Daniel Jacobowitz
2002-03-11 6:54 ` Michal Ludvig
2002-03-11 7:37 ` Daniel Jacobowitz
2002-03-11 18:22 ` Andrew Cagney
2002-03-11 18:47 ` Daniel Jacobowitz
2002-03-13 6:14 ` Michal Ludvig
2002-03-13 7:48 ` Andreas Schwab
2002-03-13 8:17 ` Michal Ludvig
2002-03-13 8:34 ` Andrew Cagney
2002-03-13 9:53 ` Andreas Schwab
2002-03-13 11:09 ` Michal Ludvig
2002-03-13 12:24 ` Andreas Schwab
2002-03-13 9:07 ` Daniel Jacobowitz
2002-03-10 12:16 ` Andrew Cagney
2002-03-11 7:08 ` Michal Ludvig
2002-03-11 7:37 ` Daniel Jacobowitz
2002-03-11 8:06 ` Michal Ludvig
2002-03-11 8:12 ` Daniel Jacobowitz
2002-03-11 8:38 ` Michal Ludvig
2002-03-11 8:34 ` Andrew Cagney
2002-03-11 7:53 ` Andrew Cagney [this message]
2002-03-11 9:12 ` Michal Ludvig
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=3C8CD30A.8070207@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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