From: Kevin Buettner <kevinb@cygnus.com>
To: Mike Brownlow <mike@wsmake.org>
Cc: GDB Discussion <gdb@sources.redhat.com>, wdb@cup.hp.com
Subject: Re: GDB TUI doesn't build
Date: Wed, 14 Feb 2001 16:24:00 -0000 [thread overview]
Message-ID: <1010215001722.ZM7044@ocotillo.lan> (raw)
In-Reply-To: <20010214174509.A14430@ctelcom.net>
On Feb 14, 5:45pm, Mike Brownlow wrote:
> I thought this would be a good opportunity to raise a question I
> have about the TUI in GDB. I have recently registered my libtui as a
> project on freshmeat, before I knew that my favorite debugger had
> a libtui in it. I'm wondering if this would cause problems for
> anybody? Should I change my lib's name? Or will it not be a big
> deal? I don't want to use libtui if the plans for GDB libtui are
> to release it separately or if GDB programmers dislike the idea of my
> lib having the same name. Obviously GDB TUI has been around longer,
> but I wanted to hear what people think about this.
>
> I honestly wasn't aware that a libtui existed yet, but I'm willing
> to change the name for my favorite debugger. :)
>
> My lib is at: http://www.wsmake.org/~mike/software/libtui/
Mike,
I don't think there's any need for you to change the name of your
library. GDB's TUI will likely stay confined to GDB so I doubt that
there will be much confusion.
Kevin
next prev parent reply other threads:[~2001-02-14 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 2:38 Richard Shih-Ping Chan
[not found] ` <3A59DBFD.19EED398@cygnus.com>
[not found] ` <20010108165633.F26870@dublin.int.act-europe.fr>
[not found] ` <3A5ECA3A.68979DAC@cygnus.com>
[not found] ` <20010112180217.A23207@cshihpin.isl.dso>
2001-02-14 12:34 ` Andrew Cagney
2001-02-14 15:55 ` Mike Brownlow
2001-02-14 16:24 ` Kevin Buettner [this message]
2001-02-14 18:53 ` Mike Brownlow
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=1010215001722.ZM7044@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=mike@wsmake.org \
--cc=wdb@cup.hp.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