From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] [4/4] Remove libgdb API (gdb.h & doc)
Date: Sat, 14 Jan 2012 10:47:00 -0000 [thread overview]
Message-ID: <83d3amk7ws.fsf@gnu.org> (raw)
In-Reply-To: <4F108D23.5050803@redhat.com>
> Date: Fri, 13 Jan 2012 11:59:31 -0800
> From: Keith Seitz <keiths@redhat.com>
>
> This final patch simply removes the gdb.h and removes mention of it from
> the makefile and gdbint.texinfo.
> [...]
> -@subheading Library - @file{gdb.h}
> -@file{libgdb} is the most obvious component of this system. It provides
> -the query interface. Each function is parameterized by a @code{ui-out}
> -builder. The result of the query is constructed using that builder
> -before the query function returns.
I admit I don't really understand where all this is going. We are not
removing libgdb itself, are we? If we are, there are many more
references to libgdb in the manual that need to be removed or
rewritten.
If we are not removing libgdb, but only gdb.h, then I have 2
questions:
. Why does it make sense to remove gdb.h, if the library is going to
stay?
. The text you remove above speaks about libgdb; gdb.h is just
mentioned as the related header. Even if gdb.h is going to be
removed, it doesn't make sense IMO to remove the description of
libgdb itself, because otherwise the rest of this section will
make no sense at all. The section's name, let me remind you, is
"libgdb components", so how omitting libgdb itself from the
discussion could possibly be TRT? E.g., all those references to
"queries" will have no real meaning.
What am I missing?
next prev parent reply other threads:[~2012-01-14 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 20:20 Keith Seitz
2012-01-14 10:47 ` Eli Zaretskii [this message]
2012-01-16 17:24 ` Tom Tromey
2012-01-16 17:28 ` Eli Zaretskii
2012-01-16 17:17 ` Tom Tromey
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=83d3amk7ws.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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