From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6304 invoked by alias); 10 Apr 2002 05:33:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6283 invoked from network); 10 Apr 2002 05:32:59 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 10 Apr 2002 05:32:59 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id JAA21095; Wed, 10 Apr 2002 09:31:35 +0300 (IDT) Date: Tue, 09 Apr 2002 22:33:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Jim Ingham cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: add set cp-abi command In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00395.txt.bz2 On Tue, 9 Apr 2002, Jim Ingham wrote: > I got distracted from this for a little while... Here is a final > version with something in the texi file as well. Thanks. Some comments about the doco patch: > + @kindex set cp-abi > + @item set cp-abi > + @itemx set cp-abi auto > + Set the C++ ABI that gdb will use to decode C++ objects. The default is "auto" > + which means gdb will assume the gnu-v2 ABI unless it sees symbols that > + look like the gnu-v3 ABI, in which case it will switch to the gnu-v3 ABI. With > + no arguments, list the available C++ ABIs. Please explain in a few words what "ABI" means; I don't think Joe Random C++ User will necessarily know that. A list of possible values one can use (in addition to "auto") is also something the manual should have. (Btw, I think that the built-in documentation of the "set abi" command could also use a word of explanation of the term "ABI".) Please change "auto" to ``auto'' (this looks much prettier in the printed version, and is translated into "auto" in the Info output), and please use C@t{++} instead of C++ (also for aesthetic reasons). Finally, we use `@value{GDBN}' instead of just `gdb' throughout the manual (evidently to allow custom versions of manuals for GDB that is named differently).