This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: el vs ell (Re: Static tracepoints support)
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org, Eli Zaretskii <eliz at gnu dot org>
- Date: Thu, 1 Jul 2010 18:28:03 +0100
- Subject: Re: el vs ell (Re: Static tracepoints support)
- References: <201006251931.57860.pedro@codesourcery.com> <201007011449.54153.pedro@codesourcery.com> <83r5jn9ljm.fsf@gnu.org>
On Thursday 01 July 2010 18:09:01, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Thu, 1 Jul 2010 14:49:53 +0100
> > Cc: Eli Zaretskii <eliz@gnu.org>
> >
> > As promised.. There is only one other instance of "el" or "ell" in
> > the manuals or sources I could find (cd gdb; egrep " el(l)?(,|\.| )" * -rn),
> > and it was the one I copied from. I was going to fix it, but, I noticed
> > that <http://en.wikipedia.org/wiki/L> says:
> >
> > "L is the twelfth letter of the basic modern Latin alphabet. Its name in
> > English (play /ËÉl/) is spelled el or occasionally ell.[1]"
> >
> > So, which one should we use? Is this an American English vs other
> > flavours issue?
>
> I don't know about flavors, but every instance I saw used "ell".
>
googling for "lowercase el", I see a bunch. In fact aproximatly
50/50 vs ell. Anyway, I've applied the patch below to make us
use ell in both cases.
On Thursday 01 July 2010 17:26:08, Michael Snyder wrote:
> You could just say "lower-case 'L'"...
the sentense in question goes:
"with l (lower-case ell, for last)"
--
Pedro Alves
2010-07-01 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (General Query Packets) <qfThreadInfo,
qsThreadInfo>: Spell out `l' as ell.
---
gdb/doc/gdb.texinfo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo 2010-07-01 18:19:10.000000000 +0100
+++ src/gdb/doc/gdb.texinfo 2010-07-01 18:20:07.000000000 +0100
@@ -31744,7 +31744,7 @@ In response to each query, the target wi
more thread IDs, separated by commas.
@value{GDBN} will respond to each reply with a request for more thread
ids (using the @samp{qs} form of the query), until the target responds
-with @samp{l} (lower-case el, for @dfn{last}).
+with @samp{l} (lower-case ell, for @dfn{last}).
Refer to @ref{thread-id syntax}, for the format of the @var{thread-id}
fields.