From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/MI] Renumber enum mi_cmd_result
Date: Mon, 20 May 2002 10:34:00 -0000 [thread overview]
Message-ID: <3CE93391.5060500@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0205201000310.20482-100000@makita.cygnus.com>
>
> Ugh. This turned out to be more elusive than I thought. After trying this
> and that to untangle captured_mi_execute_command and catch_errors
> (mi_execute_command used a return code that was a hybrid of both of
> these), I've settled on the following patch, which at least attempts to
> keep the mi return result of the command separate from what
> mi_execute_command should do.
>
Looks like a good move. Yes.
Andrew
PS: catch_exceptions() is something of a compromise so I'm not suprized.
One early prototype had the wrapped function returning void so code
was forced to pass the result back via the argument.
next prev parent reply other threads:[~2002-05-20 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 14:29 Keith Seitz
2002-05-17 14:43 ` Andrew Cagney
2002-05-17 14:47 ` Keith Seitz
2002-05-20 10:08 ` Keith Seitz
2002-05-20 10:34 ` Andrew Cagney [this message]
2002-05-20 11:10 ` Keith Seitz
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=3CE93391.5060500@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@redhat.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