Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: keiths@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] [4/4] Remove libgdb API (gdb.h & doc)
Date: Mon, 16 Jan 2012 17:28:00 -0000	[thread overview]
Message-ID: <83fwffimn1.fsf@gnu.org> (raw)
In-Reply-To: <m3aa5nr2e5.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
> Date: Mon, 16 Jan 2012 10:19:30 -0700
> 
> Eli>   . Why does it make sense to remove gdb.h, if the library is going to
> Eli>     stay?
> 
> gdb.h declares a few wrappers that follow a different exception
> convention from the rest of gdb.  However, there aren't enough of these
> wrappers to actually interface any client program with the rest of gdb;
> clients in practice will have to use the other exception handling
> mechanism.  So, at present this stuff serves to obfuscate more than
> help.  Also, I don't think anybody is going to, or should, work on
> extending this interface.
> 
> So, removing this is a cleanup.  It helps make gdb more regular.

Thanks for the explanations.

In that case, I think the change to the manual went one notch too far:
it should only remove references to gdb.h, but not to libgdb itself.
IOW, rephrase the text that references gdb.h and libgdb such that it
references only the latter.

TIA


  reply	other threads:[~2012-01-16 17:27 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
2012-01-16 17:24   ` Tom Tromey
2012-01-16 17:28     ` Eli Zaretskii [this message]
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=83fwffimn1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tromey@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