From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15013 invoked by alias); 16 Jan 2012 17:27:11 -0000 Received: (qmail 14999 invoked by uid 22791); 16 Jan 2012 17:27:10 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL,TW_BG X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 16 Jan 2012 17:26:57 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0LXW00G00J20P200@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Mon, 16 Jan 2012 19:26:50 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.127.91.164]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LXW00CBLJ4PJQG1@a-mtaout22.012.net.il>; Mon, 16 Jan 2012 19:26:50 +0200 (IST) Date: Mon, 16 Jan 2012 17:28:00 -0000 From: Eli Zaretskii Subject: Re: [RFA] [4/4] Remove libgdb API (gdb.h & doc) In-reply-to: To: Tom Tromey Cc: keiths@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83fwffimn1.fsf@gnu.org> References: <4F108D23.5050803@redhat.com> <83d3amk7ws.fsf@gnu.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00559.txt.bz2 > From: Tom Tromey > Cc: Keith Seitz , 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