This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[doc] Re: [RFC] s/preceed/precede/
- From: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches ml <gdb-patches at sourceware dot org>, Eli Zaretskii <eliz at gnu dot org>
- Date: Mon, 04 Jul 2011 16:56:12 -0300
- Subject: [doc] Re: [RFC] s/preceed/precede/
- References: <1309807927.4471.12.camel@hactar> <20110704194610.GR2407@adacore.com>
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 <bauerman.ibm.com>
> >
> > 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