From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20316 invoked by alias); 4 Jul 2011 19:56:39 -0000 Received: (qmail 20308 invoked by uid 22791); 4 Jul 2011 19:56:39 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from e24smtp02.br.ibm.com (HELO e24smtp02.br.ibm.com) (32.104.18.86) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 Jul 2011 19:56:23 +0000 Received: from mailhub1.br.ibm.com (mailhub1.br.ibm.com [9.18.232.109]) by e24smtp02.br.ibm.com (8.14.4/8.13.1) with ESMTP id p64L4g7J009241 for ; Mon, 4 Jul 2011 18:04:42 -0300 Received: from d24av03.br.ibm.com (d24av03.br.ibm.com [9.8.31.95]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p64JwJAx954428 for ; Mon, 4 Jul 2011 16:58:19 -0300 Received: from d24av03.br.ibm.com (loopback [127.0.0.1]) by d24av03.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p64JuJc1010993 for ; Mon, 4 Jul 2011 16:56:19 -0300 Received: from [9.8.1.40] ([9.8.1.40]) by d24av03.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p64JuJj2010990; Mon, 4 Jul 2011 16:56:19 -0300 Subject: [doc] Re: [RFC] s/preceed/precede/ From: Thiago Jung Bauermann To: Joel Brobecker Cc: gdb-patches ml , Eli Zaretskii In-Reply-To: <20110704194610.GR2407@adacore.com> References: <1309807927.4471.12.camel@hactar> <20110704194610.GR2407@adacore.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 04 Jul 2011 20:02:00 -0000 Message-ID: <1309809372.4471.20.camel@hactar> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: 2011-07/txt/msg00123.txt.bz2 On Mon, 2011-07-04 at 12:46 -0700, Joel Brobecker wrote: > > It looks like "preceed" is wrong and "precede" is right. I can't find > > "preceed" in neither Merriam-Webster nor dictionary.com. Also, there are > > many places using "precede" in GDB's source code. > > > > But "preceed" is so common that I'm not so sure about this patch. > > Perhaps it's just an alternative spelling? > > As far as I can tell "preceed" is not correct. In fact, I can see > pages where this is explicitly listed as a mispelling. For instance, > the following Wikipedia page: > http://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machines > And I found evidence that he same fix was made in the ZSH code. Thanks for the research! > > 2011-07-04 Thiago Jung Bauermann > > > > gdb/ > > * ada-lang.c: Fix typos. > > * amd64-tdep.c: Likewise. > > * breakpoint.c: Likewise. > > * cli/cli-decode.c: Likewise. > > * findcmd.c: Likewise. > > * inline-frame.c: Likewise. > > * mi/mi-main.c: Likewise. > > * minsyms.c: Likewise. > > * monitor.c: Likewise. > > * monitor.h: Likewise. > > * prologue-value.c: Likewise. > > * reverse.c: Likewise. > > * s390-tdep.c: Likewise. > > > > gdb/testsuite/ > > * gdb.base/call-sc.c: Likewise. > > * gdb.base/ifelse.exp: Likewise. > > * gdb.base/structs.c: Likewise. > > > > gdb/doc/ > > * gdb.texinfo: Likewise. > > OK. Great. I forgot to mention that two of these typos are in error messages. One related to the break-range command: - error (_("Invalid address range, end preceeds start.")); + error (_("Invalid address range, end precedes start.")); and the other related to the find command: - error (_("Invalid search space, end preceeds start.")); + error (_("Invalid search space, end precedes start.")); Does it matter? I guess not, since we only support parseable output in the MI. Also, I forgot to mark in the subject that this touches the documentation, so I'm copying Eli. -- []'s Thiago Jung Bauermann IBM Linux Technology Center