From: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
To: gdb-patches@sourceware.org, pedro_alves@portugalmail.pt,
ambrogino.modigliani@gmail.com, ambrogino.modigliani@mail.com
Subject: [PATCH v2 09/12] Fix spelling in comments in .l files (gdb)
Date: Thu, 01 Dec 2016 07:26:00 -0000 [thread overview]
Message-ID: <1480577171-2450-10-git-send-email-ambrogino.modigliani@mail.com> (raw)
In-Reply-To: <1480577171-2450-1-git-send-email-ambrogino.modigliani@mail.com>
gdb/ChangeLog:
* ada-lex.l: Fix spelling in comments.
---
gdb/ada-lex.l | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/ada-lex.l b/gdb/ada-lex.l
index 03204ff..05e663d 100644
--- a/gdb/ada-lex.l
+++ b/gdb/ada-lex.l
@@ -320,7 +320,7 @@ canonicalizeNumeral (char *s1, const char *s2)
/* Interprets the prefix of NUM that consists of digits of the given BASE
as an integer of that BASE, with the string EXP as an exponent.
Puts value in yylval, and returns INT, if the string is valid. Causes
- an error if the number is improperly formated. BASE, if NULL, defaults
+ an error if the number is improperly formatted. BASE, if NULL, defaults
to "10", and EXP to "1". The EXP does not contain a leading 'e' or 'E'.
*/
@@ -414,7 +414,7 @@ processReal (struct parser_state *par_state, const char *num0)
NAME0 contains the substring "___", it is assumed to be already
encoded and the resulting name is equal to it. Otherwise, it differs
from NAME0 in that:
- + Characters between '...' or <...> are transfered verbatim to
+ + Characters between '...' or <...> are transferred verbatim to
yylval.ssym.
+ <, >, and trailing "'" characters in quoted sequences are removed
(a leading quote is preserved to indicate that the name is not to be
--
2.7.4
next prev parent reply other threads:[~2016-12-01 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:26 [PATCH v2 00/12] Fix spelling in comments - GDB Ambrogino Modigliani
2016-12-01 7:26 ` [PATCH v2 04/12] Fix spelling in comments in Assembler files (gdb) Ambrogino Modigliani
2016-12-01 7:26 ` Ambrogino Modigliani [this message]
2016-12-01 7:27 ` [PATCH v2 08/12] Fix spelling in comments in .in files (opcodes) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 02/12] Fix spelling in comments in C source files (gdb) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 12/12] Fix spelling in comments in .tbl files (opcodes) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 07/12] Fix spelling in comments in .cpu files (cpu) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 01/12] Fix spelling in comments in C source files (bfd) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 06/12] Fix spelling in comments in XML files (gdb) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 10/12] Fix spelling in comments in .opc files (cpu) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 11/12] Fix spelling in comments in .opc files (opcodes) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 05/12] Fix spelling in comments in Expect scripts (gdb) Ambrogino Modigliani
2016-12-01 7:27 ` [PATCH v2 03/12] Fix spelling in comments in C source files (opcodes) Ambrogino Modigliani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1480577171-2450-10-git-send-email-ambrogino.modigliani@mail.com \
--to=ambrogino.modigliani@gmail.com \
--cc=ambrogino.modigliani@mail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).