From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] gdbadmin/ss/gdb_ari.sh update UCASE rule
Date: Tue, 14 Apr 2009 21:49:00 -0000 [thread overview]
Message-ID: <007201c9bd4a$e64c9d20$b2e5d760$@u-strasbg.fr> (raw)
The current UCASE rule
triggers lost of false warnings
as for instance
gdb/breakpoint.c:8522: code: UCASE function: Function name is uppercase.
gdb/breakpoint.c:8520: /* Create a vector of all tracepoints. */
gdb/breakpoint.c:8521:
gdb/breakpoint.c:8522: VEC(breakpoint_p) *
gdb/breakpoint.c:8523: all_tracepoints ()
gdb/breakpoint.c:8524: {
I propose a rule that only looks for:
a function name starting with a capital letter at the start
of the line, followed by a open brace, optionally parameters, a closing
brace
and nothing else (apart from spaces)
This decreases the number of UCASE code warnings from 66 to 15.
The test is still not perfect but at least,
most VEC.* related problems are gone.
Is this OK?
Pierre Muller
Pascal language support maintainer for GDB
Index: gdb_ari.sh
===================================================================
RCS file: /cvs/gdbadmin/ss/gdb_ari.sh,v
retrieving revision 1.85
diff -u -r1.85 gdb_ari.sh
--- gdb_ari.sh 14 Apr 2009 21:19:19 -0000 1.85
+++ gdb_ari.sh 14 Apr 2009 21:42:28 -0000
@@ -461,7 +461,7 @@
Function name is uppercase."
category["UCASE function"] = ari_code
}
-/^[A-Z][[:alnum:]_]*[[:space:]]*\(/ {
+/^[A-Z][[:alnum:]_]*[[:space:]]*\([^()]*\)[[:space:]]*$/ {
if (is_yacc_or_lex == 0) {
fail("UCASE function")
}
next reply other threads:[~2009-04-14 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:49 Pierre Muller [this message]
2009-04-15 7:25 ` Eli Zaretskii
2009-04-20 16:01 ` [PATCH] gdbadmin/ss/gdb_ari.sh modify editCase/UCASE rules Pierre Muller
2009-04-20 17:15 ` Andreas Schwab
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='007201c9bd4a$e64c9d20$b2e5d760$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
/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