From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: ghost@cs.msu.su, gdb@sources.redhat.com
Subject: Re: MI error messages
Date: Fri, 10 Feb 2006 20:35:00 -0000 [thread overview]
Message-ID: <200602102034.k1AKYtI4023423@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <uirrn2q88.fsf@gnu.org> (message from Eli Zaretskii on Fri, 10 Feb 2006 17:22:31 +0200)
> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
> elgar.sibelius.xs4all.nl
> X-Spam-Level:
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=no
> version=3.1.0
> X-From_: gdb-return-24221-m.m.kettenis=alumnus.utwente.nl@sourceware.org Fri Feb 10 16:23:07 2006
> Date: Fri, 10 Feb 2006 17:22:31 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Reply-to: Eli Zaretskii <eliz@gnu.org>
> X-IsSubscribed: yes
> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
> Sender: gdb-owner@sourceware.org
> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> X-UTwente-MailScanner: Found to be clean
> X-MailScanner-From: gdb-return-24221-m.m.kettenis=alumnus.utwente.nl@sourceware.org
>
> > Date: Fri, 10 Feb 2006 08:47:01 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> >
> > 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?
>
> For consistency.
The only way we can ever be consistent is by removing them. Function
names are an implementation detail. What if we reorganize the code a
bit, changing the function name. Should we change the error message?
Or leave it as is, such that it no longer refers to the function that
actually prints that message?
Mark
next prev parent reply other threads:[~2006-02-10 20:35 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
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 [this message]
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=200602102034.k1AKYtI4023423@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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