From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 1/5] Simplify a regular expression in ada-lex.l
Date: Mon, 28 Feb 2022 11:33:00 -0700 [thread overview]
Message-ID: <20220228183304.1162089-2-tromey@adacore.com> (raw)
In-Reply-To: <20220228183304.1162089-1-tromey@adacore.com>
ada-lex.l uses "%option case-insensitive", so there is no need for
regular expressions to match upper case.
---
gdb/ada-lex.l | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/ada-lex.l b/gdb/ada-lex.l
index f61efba81a9..a1e19423691 100644
--- a/gdb/ada-lex.l
+++ b/gdb/ada-lex.l
@@ -220,7 +220,7 @@ false { return FALSEKEYWORD; }
/* ATTRIBUTES */
-{TICK}[a-zA-Z][a-zA-Z_]+ { BEGIN INITIAL; return processAttribute (yytext+1); }
+{TICK}[a-z][a-z_]+ { BEGIN INITIAL; return processAttribute (yytext+1); }
/* PUNCTUATION */
--
2.31.1
next prev parent reply other threads:[~2022-02-28 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:32 [PATCH 0/5] Handle non-ASCII identifiers in Ada Tom Tromey via Gdb-patches
2022-02-28 18:33 ` Tom Tromey via Gdb-patches [this message]
2022-02-28 18:33 ` [PATCH 2/5] Don't pre-size result string in ada_decode Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 3/5] Let phex and phex_nz handle sizeof_l==1 Tom Tromey via Gdb-patches
2022-03-01 14:26 ` Simon Marchi via Gdb-patches
2022-03-01 14:32 ` Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 4/5] Define HOST_UTF32 in charset.h Tom Tromey via Gdb-patches
2022-02-28 18:33 ` [PATCH 5/5] Handle non-ASCII identifiers in Ada Tom Tromey via Gdb-patches
2022-02-28 18:59 ` Eli Zaretskii via Gdb-patches
2022-02-28 20:59 ` Tom Tromey via Gdb-patches
2022-03-01 3:28 ` Eli Zaretskii via Gdb-patches
2022-03-01 14:49 ` Tom Tromey via Gdb-patches
2022-03-01 15:17 ` Eli Zaretskii via Gdb-patches
2022-03-01 15:33 ` Tom Tromey via Gdb-patches
2022-03-07 14:52 ` [PATCH 0/5] " Tom Tromey via Gdb-patches
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=20220228183304.1162089-2-tromey@adacore.com \
--to=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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