From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: RFA: change K&R to ISO
Date: Fri, 26 Sep 2008 23:32:00 -0000 [thread overview]
Message-ID: <m3k5cytrh1.fsf@fleche.redhat.com> (raw)
I noticed some K&R-style function definitions.
This seemed weird, so this patch changes them to ISO style.
Built & regtested on x86-64 (compile farm).
Please review.
Tom
:ADDPATCH java:
2008-09-26 Tom Tromey <tromey@redhat.com>
* jv-exp.y (insert_exp): Define using ISO syntax.
(copy_exp): Likewise.
(push_expression_name): Likewise.
(push_fieldnames): Likewise.
(java_type_from_name): Likewise.
(yyerror): Likewise.
(yylex): Likewise.
(parse_number): Likewise.
diff --git a/gdb/jv-exp.y b/gdb/jv-exp.y
index ff9a7a1..12bf517 100644
--- a/gdb/jv-exp.y
+++ b/gdb/jv-exp.y
@@ -693,11 +693,7 @@ Expression:
/*** Needs some error checking for the float case ***/
static int
-parse_number (p, len, parsed_float, putithere)
- char *p;
- int len;
- int parsed_float;
- YYSTYPE *putithere;
+parse_number (char *p, int len, int parsed_float, YYSTYPE *putithere)
{
ULONGEST n = 0;
ULONGEST limit, limit_div_base;
@@ -851,7 +847,7 @@ static const struct token tokentab2[] =
/* Read one token, getting characters through lexptr. */
static int
-yylex ()
+yylex (void)
{
int c;
int namelen;
@@ -1197,8 +1193,7 @@ yylex ()
}
void
-yyerror (msg)
- char *msg;
+yyerror (char *msg)
{
if (prev_lexptr)
lexptr = prev_lexptr;
@@ -1210,9 +1205,7 @@ yyerror (msg)
}
static struct type *
-java_type_from_name (name)
- struct stoken name;
-
+java_type_from_name (struct stoken name)
{
char *tmp = copy_name (name);
struct type *typ = java_lookup_class (tmp);
@@ -1271,8 +1264,7 @@ push_variable (struct stoken name)
qualified name (has '.'), generate a field access for each part. */
static void
-push_fieldnames (name)
- struct stoken name;
+push_fieldnames (struct stoken name)
{
int i;
struct stoken token;
@@ -1363,8 +1355,7 @@ push_qualified_expression_name (struct stoken name, int dot_index)
Handle VAR, TYPE, TYPE.FIELD1....FIELDN and VAR.FIELD1....FIELDN. */
static void
-push_expression_name (name)
- struct stoken name;
+push_expression_name (struct stoken name)
{
char *tmp;
struct type *typ;
@@ -1418,9 +1409,7 @@ push_expression_name (name)
into a freshly malloc'ed struct expression. Its language_defn is set
to null. */
static struct expression *
-copy_exp (expr, endpos)
- struct expression *expr;
- int endpos;
+copy_exp (struct expression *expr, int endpos)
{
int len = length_of_subexp (expr, endpos);
struct expression *new
@@ -1434,9 +1423,7 @@ copy_exp (expr, endpos)
/* Insert the expression NEW into the current expression (expout) at POS. */
static void
-insert_exp (pos, new)
- int pos;
- struct expression *new;
+insert_exp (int pos, struct expression *new)
{
int newlen = new->nelts;
next reply other threads:[~2008-09-26 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:32 Tom Tromey [this message]
2008-09-26 23:49 ` Pedro Alves
2008-09-27 4:14 ` Joel Brobecker
2008-09-27 20:24 ` Tom Tromey
2008-09-28 16:58 ` Joel Brobecker
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=m3k5cytrh1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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