Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [PATCH] Use TYPE_TAG_NAME everywhere
@ 2002-02-03 15:15 Daniel Jacobowitz
  2002-02-03 15:18 ` Daniel Jacobowitz
  2002-02-03 16:27 ` Andrew Cagney
  0 siblings, 2 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2002-02-03 15:15 UTC (permalink / raw)
  To: gdb-patches

One file accessed the tag_name member directly.  Just for consistency, I
fixed it to use the macro.  Committed as obvious.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.2121
diff -u -p -r1.2121 ChangeLog
--- ChangeLog	2002/02/03 22:57:56	1.2121
+++ ChangeLog	2002/02/03 23:11:03
@@ -1,5 +1,10 @@
 2002-02-03  Daniel Jacobowitz  <drow@mvista.com>
 
+	* ax-gdb.c (find_field): Use TYPE_TAG_NAME instead
+	of accessing tag_name directly.
+
+2002-02-03  Daniel Jacobowitz  <drow@mvista.com>
+
 	PR gdb/280
 	* gdbtypes.c (replace_type): New function.
 	* gdbtypes.h (replace_type): Add prototype.
Index: ax-gdb.c
===================================================================
RCS file: /cvs/src/src/gdb/ax-gdb.c,v
retrieving revision 1.11
diff -u -p -r1.11 ax-gdb.c
--- ax-gdb.c	2002/01/05 04:30:15	1.11
+++ ax-gdb.c	2002/02/03 23:11:03
@@ -1165,7 +1165,7 @@ find_field (struct type *type, char *nam
     }
 
   error ("Couldn't find member named `%s' in struct/union `%s'",
-	 name, type->tag_name);
+	 name, TYPE_TAG_NAME (type));
 
   return 0;
 }


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-02-04  0:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-03 15:15 [PATCH] Use TYPE_TAG_NAME everywhere Daniel Jacobowitz
2002-02-03 15:18 ` Daniel Jacobowitz
2002-02-03 16:27 ` Andrew Cagney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox