From: Doug Evans <dje@google.com>
To: tromey@redhat.com
Cc: Phil Muldoon <pmuldoon@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] PR python/11407
Date: Sat, 26 Jun 2010 17:10:00 -0000 [thread overview]
Message-ID: <AANLkTikpTwXRhqEc8QvJDrjHLkPSKezuT5d5zddlp6lJ@mail.gmail.com> (raw)
In-Reply-To: <m3y6e33r7d.fsf@fleche.redhat.com>
On Fri, Jun 25, 2010 at 11:25 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>
> Phil> I'm not sure what to do in this case. There seems to be no direct
> Phil> equivalent of converting an exception to error output on a stream in MI
> Phil> (or any cases of TRY ... exception handlers). There are many cases of
> Phil> MI raising an error() though, so I thought it appropriate in our case
> Phil> to raise a warning() instead. Because of the peculiarities of the MI
> Phil> cases I just report a warning generically and move on. This is not
> Phil> totally ideal, but it does allow the error/warning preamble followed
> Phil> by the actual locals information.
>
> I'm not convinced a warning is the best thing.
>
> Why not catch the exception and print the text of it as the variable's
> value? Something like <error reading variable: %s>
> I think this will work ok with existing front ends.
I like this, fwiw.
next prev parent reply other threads:[~2010-06-26 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 11:33 Phil Muldoon
2010-06-24 15:10 ` Jan Kratochvil
2010-06-24 18:10 ` Tom Tromey
2010-06-24 22:01 ` Phil Muldoon
2010-06-25 6:56 ` Phil Muldoon
2010-06-25 14:27 ` Phil Muldoon
2010-06-25 18:25 ` Tom Tromey
2010-06-25 21:20 ` Phil Muldoon
2010-07-07 17:02 ` Phil Muldoon
2010-08-09 19:41 ` Phil Muldoon
2010-08-31 18:42 ` Phil Muldoon
2010-09-08 19:25 ` Tom Tromey
2010-06-26 17:10 ` Doug Evans [this message]
2010-06-28 6:26 ` André Pönitz
2010-06-28 16:52 ` Tom Tromey
2010-06-29 7:43 ` André Pönitz
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=AANLkTikpTwXRhqEc8QvJDrjHLkPSKezuT5d5zddlp6lJ@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).