From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12340 invoked by alias); 14 May 2009 19:02:28 -0000 Received: (qmail 12188 invoked by uid 22791); 14 May 2009 19:02:27 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout3.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 14 May 2009 19:02:21 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KJN00800E7DH300@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Thu, 14 May 2009 22:02:18 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.73.80]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KJN00I3UE7RUZ50@i_mtaout3.012.net.il>; Thu, 14 May 2009 22:02:15 +0300 (IDT) Date: Thu, 14 May 2009 19:02:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] GDB/MI documentation In-reply-to: <18955.48976.690330.445604@totara.tehura.co.nz> To: nickrob@snap.net.nz (Nick Roberts) Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83vdo3qzi9.fsf@gnu.org> References: <18954.41627.111280.24736@totara.tehura.co.nz> <834ovoswt3.fsf@gnu.org> <18955.48976.690330.445604@totara.tehura.co.nz> 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: 2009-05/txt/msg00307.txt.bz2 > Date: Thu, 14 May 2009 18:50:56 +1200 > Cc: gdb-patches@sourceware.org > From: nickrob@snap.net.nz (Nick Roberts) > > > > Here are just a few basic changes that preserve the content. > > > > I'm okay with adding nodes, but the rest of the changes don't make the > > text any clearer than it is already. > > I thought this change was so basic, obvious almost, that approval would be a > formality. If you feel strongly about them, go ahead and commit them, but I still think that the new text is not any clearer or more correct than the original one. Anyway, I thought you wanted to suggest some real additions to the manual. That would be most welcome, thanks. > - Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three > - parts---commands sent to @value{GDBN}, responses to those commands > - and notifications. > > + Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three > + parts: commands sent to @value{GDBN}; responses to those commands; > + and notifications. > > A wide dash (Em dash?) is normally used parenthetically while a semi-colon is > generally used for a list, often with a colon. The example at > http://en.wikipedia.org/wiki/Semicolon: > > "She saw three men: Donald, who came from New Zealand; Jon, the milkman's son; > and George, a gaunt kind of man." > > is almost identical to my change. No, it isn't: in the example from Wiki, there are commas ("Donald, who came..."), so using semi-colons disambiguates the intent. In the GDB manual case, there are no commas to create ambiguity in the first place, so commas are okay, IMO. > It's generally considered bad English to use "is" after a plural word. You are right about this one. > > > I think it would be quite easy to read GDB/MI General Design and still not > > > understand the overall purpose of GDB/MI. > > > > Feel free to suggest the text you think is missing. I'd welcome any > > such patches. > > > > TIA > > Frankly, the overhead seems too high. That's because the changes you submitted are insignificant. For real changes of content, I can assure you that there will be no more iterations than necessary. You can try looking through submissions by others and my review of them.