Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH RFC] Protoize values.c, varobj.c
Date: Tue, 07 Nov 2000 21:21:00 -0000	[thread overview]
Message-ID: <1001108052055.ZM20567@ocotillo.lan> (raw)

More protoization...

	* values.c (value_being_returned, using_struct_return): Protoize.
	* varobj.c (child_exists, cplus_class_num_children): Protoize.

Index: values.c
===================================================================
RCS file: /cvs/src/src/gdb/values.c,v
retrieving revision 1.10
diff -u -r1.10 values.c
--- values.c	2000/10/30 15:32:51	1.10
+++ values.c	2000/11/08 05:16:31
@@ -1466,12 +1466,9 @@
    0 when it is using the value returning conventions (this often
    means returning pointer to where structure is vs. returning value). */
 
+/* ARGSUSED */
 value_ptr
-value_being_returned (valtype, retbuf, struct_return)
-     register struct type *valtype;
-     char *retbuf;
-     int struct_return;
-     /*ARGSUSED */
+value_being_returned (struct type *valtype, char *retbuf, int struct_return)
 {
   register value_ptr val;
   CORE_ADDR addr;
@@ -1530,13 +1527,10 @@
    is the type returned by the function.  GCC_P is nonzero if compiled
    with GCC.  */
 
+/* ARGSUSED */
 int
-using_struct_return (function, funcaddr, value_type, gcc_p)
-     value_ptr function;
-     CORE_ADDR funcaddr;
-     struct type *value_type;
-     int gcc_p;
-     /*ARGSUSED */
+using_struct_return (value_ptr function, CORE_ADDR funcaddr,
+		     struct type *value_type, int gcc_p)
 {
   register enum type_code code = TYPE_CODE (value_type);
 
Index: varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.11
diff -u -r1.11 varobj.c
--- varobj.c	2000/11/06 23:12:29	1.11
+++ varobj.c	2000/11/08 05:16:35
@@ -1216,9 +1216,7 @@
 /* Does a child with the name NAME exist in VAR? If so, return its data.
    If not, return NULL. */
 static struct varobj *
-child_exists (var, name)
-     struct varobj *var;	/* Parent */
-     char *name;		/* name of child */
+child_exists (struct varobj *var, char *name)
 {
   struct varobj_child *vc;
 
@@ -2156,9 +2154,7 @@
    That means we need to descend into all baseclasses and find out
    how many are there, too. */
 static void
-cplus_class_num_children (type, children)
-     struct type *type;
-     int children[3];
+cplus_class_num_children (struct type *type, int children[3])
 {
   int i;


             reply	other threads:[~2000-11-07 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07 21:21 Kevin Buettner [this message]
2000-11-09 17:27 ` Kevin Buettner

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=1001108052055.ZM20567@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb-patches@sources.redhat.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