This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[libiberty] Minor markup fix
- From: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
- To: patch <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 11 Jan 2005 20:35:09 +0100
- Subject: [libiberty] Minor markup fix
I spotted this while looking for some documentation on libiberty's hashtable
implementation: 'unsigned int hex_value' is marked up as if only unsigned was
a keyword. After struggling for a while trying to figure out libiberty's
documentation generation, which finally launched my computer into a complete
bootstrap (why does 'make info' do that???), I decided that my time is much
better spent on other stuff, and someone who knows what to do will figure this
out in seconds.
So please perform the necessary steps after verifying for yourself the
correctness of this patch. Thanks.
- Tobi
2005-01-11 Tobias Schl"uter <tobias.schlueter@physik.uni-muenchen.de>
* hex.c (hex_value): Group 'unsigned int' together to get correct
markup.
Index: hex.c
===================================================================
RCS file: /cvs/gcc/gcc/libiberty/hex.c,v
retrieving revision 1.7
diff -u -p -r1.7 hex.c
--- hex.c 22 Jun 2003 15:59:49 -0000 1.7
+++ hex.c 11 Jan 2005 19:29:59 -0000
@@ -44,7 +44,7 @@ or zero if it is not. Note that the val
@end deftypefn
-@deftypefn Extension unsigned int hex_value (int @var{c})
+@deftypefn Extension {unsigned int} hex_value (int @var{c})
Returns the numeric equivalent of the given character when interpreted
as a hexidecimal digit. The result is undefined if you pass an