From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
Subject: Re: MI error messages
Date: Fri, 10 Feb 2006 15:00:00 -0000 [thread overview]
Message-ID: <20060210145950.GA23266@nevyn.them.org> (raw)
In-Reply-To: <200602101703.35029.ghost@cs.msu.su>
On Fri, Feb 10, 2006 at 05:03:34PM +0300, Vladimir Prus wrote:
> On Friday 10 February 2006 16:47, Daniel Jacobowitz wrote:
> > On Fri, Feb 10, 2006 at 01:54:08PM +0200, Eli Zaretskii wrote:
> > > > From: Vladimir Prus <ghost@cs.msu.su>
> > > > Date: Fri, 10 Feb 2006 14:35:08 +0300
> > > >
> > > > 1. Is it guaranteed that all MI error message start with function name
> > > > and a semicolon?
> > >
> > > I see a small number of error messages that don't, but those are
> > > probably bugs that need to be fixed.
> >
> > Really? Why? I don't think the function name adds much value in
> > user-level error messages. Internal errors, sure.
>
> Does it mean that function names should be removed from error messages to
> user?
I have no idea. Personally, I think they should be.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-10 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 11:36 Vladimir Prus
2006-02-10 11:54 ` Eli Zaretskii
2006-02-10 13:47 ` Daniel Jacobowitz
2006-02-10 14:03 ` Vladimir Prus
2006-02-10 15:00 ` Daniel Jacobowitz [this message]
2006-02-10 20:31 ` Mark Kettenis
2006-02-10 15:22 ` Eli Zaretskii
2006-02-10 15:26 ` Daniel Jacobowitz
2006-02-10 15:45 ` Eli Zaretskii
2006-02-10 20:35 ` Mark Kettenis
2006-02-12 7:49 ` Jim Blandy
2006-02-12 9:22 ` Nick Roberts
2006-02-10 20:17 ` Nick Roberts
2006-02-13 7:05 ` Vladimir Prus
2006-02-13 7:43 ` Nick Roberts
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=20060210145950.GA23266@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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