From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Fri, 08 Oct 2004 08:40:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20041008085113.01d8eb60@NT_SERVER> (raw)
In-Reply-To: <20041007192830.GE14573@white>
>> >Understood, here is what I am hoping for at a minimum.
>> >
>> > * GDB supports at least 1 MI protocol for an official release.
>> > Supporting multiple MI protocols would be better for me, but
>> > not a requirement. If GDB could support multiple protocols it
>> > would improve the chances of a given front end working with a
>> > given GDB.
>>
>> But by "support" what do you mean - even a dictionary definition. GDB
>> includes at least one MI implementation, but that says nothing about how
>> well it is either implemented or supported.
>
>That's a good question.
>
>Well, by support I simply mean, GDB is officially saying that a
>particular MI protocol is implemented as it should be, that it is tested
>to make sure that it works to the best of the GDB developers knowledge and
>that it is safe to use by front ends.
>
>I am assuming that MI protocols in development ( right after a version
>bump, but before a major release ) is considered unsupported. By this I
>guess I mean that it should not be used by front ends until it is
>stable. Maybe a better word for "support" in this context is "stable".
I think the implementation grade is quite important. Though mi2 is
considered now the official and stable mi version I find that half of it
is unimplemented which makes it somehow useless for me. From
this point of view I'd say mi2 is the development version.
(And yes, I'm not only complaining, I have started implementing some
of the missing mi functions.)
Thanks
bye Fabi
next prev parent reply other threads:[~2004-10-08 6:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 20:13 Andrew Cagney
2004-10-06 22:36 ` Bob Rossi
2004-10-07 2:40 ` Andrew Cagney
2004-10-07 17:20 ` Bob Rossi
2004-10-07 20:50 ` Andrew Cagney
2004-10-07 22:42 ` Bob Rossi
2004-10-08 8:40 ` Fabian Cenedese [this message]
2004-10-08 13:17 ` Bob Rossi
2004-10-08 7:17 ` Bob Rossi
2004-10-08 12:41 ` Eli Zaretskii
2004-10-08 13:23 ` Bob Rossi
2004-10-08 13:42 ` Eli Zaretskii
2004-10-08 16:34 ` Daniel Jacobowitz
2004-10-08 16:28 ` Daniel Jacobowitz
2004-10-08 18:57 ` Eli Zaretskii
2004-10-09 11:14 ` Andrew Cagney
2004-10-10 4:06 ` Bob Rossi
2004-10-11 2:00 ` Bob Rossi
2004-10-11 14:12 ` Andrew Cagney
2004-10-11 17:22 ` Bob Rossi
2004-10-12 22:15 ` Michael Chastain
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=5.2.0.9.1.20041008085113.01d8eb60@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@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