From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Bob Rossi <bob@brasko.net>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: tests for MI commands
Date: Wed, 27 Jul 2005 22:09:00 -0000 [thread overview]
Message-ID: <17128.1691.223360.139122@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050727214911.GA21072@nevyn.them.org>
> > I think that we should either remove them (my preference) or rewrite
> > parts of GDB so that the different MI levels act as independent
> > interpreters (which currently I am certainly not going to offer to do).
> > If they were independent then clearly changing the behaviour of the
> > current level, as I have just done, wouldn't break the tests for level 2.
>
> Incorrect. Please read again my description of how you broke the mi2
> tests. It has nothing to do with your changes to the MI output and
> everything to do with your changes to the test cases.
Yes, you're right, I was too eager and my analysis is wrong for this case. My
original point, that separate mi2 tests are not worthwhile, still stands,
however.
Nick
next prev parent reply other threads:[~2005-07-27 22:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 4:51 Nick Roberts
2005-07-24 21:19 ` Daniel Jacobowitz
2005-07-26 23:31 ` Nick Roberts
2005-07-27 0:27 ` Daniel Jacobowitz
2005-07-27 3:04 ` Nick Roberts
2005-07-27 3:55 ` Daniel Jacobowitz
2005-07-27 11:46 ` Nick Roberts
2005-07-27 12:50 ` Bob Rossi
2005-07-27 20:52 ` Nick Roberts
2005-07-27 21:49 ` Daniel Jacobowitz
2005-07-27 22:09 ` Nick Roberts [this message]
2005-07-27 21:03 ` Mark Kettenis
2005-07-27 22:23 ` Nick Roberts
2005-07-28 0:08 ` Paul Gilliam
2005-07-28 0:18 ` Stan Shebs
2005-07-28 0:21 ` Daniel Jacobowitz
2005-07-28 1:39 ` Nick Roberts
2005-07-31 22:11 ` Daniel Jacobowitz
2005-07-31 23:32 ` Nick Roberts
2005-08-01 1:55 ` Daniel Jacobowitz
2005-07-27 21:25 ` Mark Kettenis
2005-07-29 7:32 ` Nick Roberts
2005-07-31 21:25 ` Daniel Jacobowitz
2005-07-31 23:32 ` Nick Roberts
2005-08-01 1:57 ` Daniel Jacobowitz
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=17128.1691.223360.139122@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=drow@false.org \
--cc=gdb-patches@sources.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