Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	jingham@apple.com, gdb@sources.redhat.com, cagney@redhat.com,
	ezannoni@redhat.com, fnasser@redhat.com
Subject: Re: MI rules
Date: Thu, 30 Sep 2004 20:42:00 -0000	[thread overview]
Message-ID: <20040930204229.GE2271@white> (raw)
In-Reply-To: <415C35ED.2070609@gnu.org>

On Thu, Sep 30, 2004 at 12:35:57PM -0400, Andrew Cagney wrote:
> FYI,
> 
> While I've been very carefully following this thread, I've not yet seen 
> a compelling reason to step into the debate.  I think JimI's already 
> addressed the issues (thanks), and pointed to where things should go.

I still think that we need to add tags to the MI interface, especially
for asynchronous MI output commands ( notifications ). Can this be
discussed with the maintainers and front end developers?

Andrew, you have been the only maintainer that has responded, and I am
grateful for that. However, you simply answer with "no", and I
personally get the impression you are not taking the matters I am
bringing up seriously.

For instance, 

   1. I am bringing up the fact that I need a tag for MI output commands
   that are asynchronous (notifications). I also said that I would prefer 
   to have it for all of them, because then I wouldn't need to play around 
   with the "tokens" at all.

   2. You respond by saying
   "I think others have already responded to this proposal with a clear
   rationale for not making a change."

   3. While I talk to Jim more about it, I find that he has tags in his
   local version of GDB for MI output commands that are asynchronous.
   They do this because they need exactly what I need.

So, two front end developers have independently come across the same
need out of MI. Unfortunately, I don't have the resources to take GDB,
patch it and distribute it with CGDB.

Honestly, I am only interested in making MI better for everyone.
Hopefully we can resolve these issues for the better of GDB. If you
think that this particular feature should not go into GDB, I would
really appreciate to at least be told the way to do what I'm trying to
do with the current MI interface.

Thanks,
Bob Rossi


  reply	other threads:[~2004-09-30 20:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1095954341.19418.ezmlm@sources.redhat.com>
2004-09-23 18:23 ` Jim Ingham
2004-09-25  1:05   ` Bob Rossi
2004-09-25 19:01     ` Jim Ingham
2004-09-25 20:12       ` Bob Rossi
2004-09-27 17:39         ` Jim Ingham
2004-09-29  3:00           ` Bob Rossi
2004-09-29 16:13             ` Jim Ingham
2004-09-29 17:27               ` Bob Rossi
2004-09-30 13:26             ` Eli Zaretskii
2004-09-30 16:21               ` Bob Rossi
2004-09-30 16:36                 ` Andrew Cagney
2004-09-30 20:42                   ` Bob Rossi [this message]
     [not found] <5733AD9C-0CF7-11D9-8325-000A9569836A@brasko.net>
2004-09-23  0:31 ` Jason Molenda
2004-09-22 13:40 Fabian Cenedese
2004-09-22 13:48 ` Bob Rossi
2004-09-22 14:10   ` Fabian Cenedese
2004-09-22 14:43     ` Bob Rossi
2004-09-22 15:01       ` Fabian Cenedese
2004-09-22 14:58     ` Alain Magloire
2004-09-22 16:18       ` Bob Rossi
2004-09-22 16:59         ` Alain Magloire

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=20040930204229.GE2271@white \
    --to=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=cagney@redhat.com \
    --cc=eliz@gnu.org \
    --cc=ezannoni@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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