From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>,
Stephane Carrez <Stephane.Carrez@worldnet.fr>
Subject: RFC: Obsolete TUI _before_ 5.1?
Date: Wed, 27 Jun 2001 20:50:00 -0000 [thread overview]
Message-ID: <3B3AA98E.9000706@cygnus.com> (raw)
Hello,
Up until now I've been of the opinion that the TUI should be left alone
until after 5.1. Given that I've dragged my feet on 5.1, I'm thinking
that the question should be re-considered.
The person I'm really interested in hearing an opinion from is Stephane
since he played with the TUI a little and got it to build. Stephane, do
you think that the TUI is salvageable or that a re-implementation would
be better.
One thing to keep in mind is that we're (I'm?) trying to reduce the
number of interfaces into GDB core with ui-out/ui-file and ``libgdb''
becomming the only interfaces. For the TUI to survive it would need a
major rewrite anyway.
Andrew
next reply other threads:[~2001-06-27 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 20:50 Andrew Cagney [this message]
2001-06-28 15:19 ` Stephane Carrez
2001-06-28 15:37 ` Andrew Cagney
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=3B3AA98E.9000706@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Stephane.Carrez@worldnet.fr \
--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