From: "Eli Zaretskii" <eliz@gnu.org>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: [PATCH] Fix deftypefn in fopen_unlocked.c
Date: Sat, 14 May 2005 09:23:00 -0000 [thread overview]
Message-ID: <01c55862$Blat.v2.4$44a795c0@zahav.net.il> (raw)
More of the same:
2005-05-14 Eli Zaretskii <eliz@gnu.org>
* fopen_unlocked.c: Enclose multi-word data types in @deftypefn in
braces.
Index: libiberty/fopen_unlocked.c
===================================================================
RCS file: /cvs/src/src/libiberty/fopen_unlocked.c,v
retrieving revision 1.4
diff -u -r1.4 fopen_unlocked.c
--- libiberty/fopen_unlocked.c 10 May 2005 15:33:33 -0000 1.4
+++ libiberty/fopen_unlocked.c 14 May 2005 08:53:13 -0000
@@ -36,7 +36,7 @@
@end deftypefn
-@deftypefn Extension FILE * fopen_unlocked (const char *@var{path}, const char * @var{mode})
+@deftypefn Extension {FILE *} fopen_unlocked (const char *@var{path}, const char * @var{mode})
Opens and returns a @code{FILE} pointer via @code{fopen}. If the
operating system supports it, ensure that the stream is setup to avoid
@@ -45,7 +45,7 @@
@end deftypefn
-@deftypefn Extension FILE * fdopen_unlocked (int @var{fildes}, const char * @var{mode})
+@deftypefn Extension {FILE *} fdopen_unlocked (int @var{fildes}, const char * @var{mode})
Opens and returns a @code{FILE} pointer via @code{fdopen}. If the
operating system supports it, ensure that the stream is setup to avoid
@@ -54,7 +54,7 @@
@end deftypefn
-@deftypefn Extension FILE * freopen_unlocked (const char * @var{path}, const char * @var{mode}, FILE * @var{stream})
+@deftypefn Extension {FILE *} freopen_unlocked (const char * @var{path}, const char * @var{mode}, FILE * @var{stream})
Opens and returns a @code{FILE} pointer via @code{freopen}. If the
operating system supports it, ensure that the stream is setup to avoid
next reply other threads:[~2005-05-14 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 9:23 Eli Zaretskii [this message]
2005-05-15 16:37 ` Ian Lance Taylor
2005-05-15 17:04 ` Andreas Jaeger
2005-05-15 17:44 ` Joseph S. Myers
2005-05-15 18:08 ` Andreas Jaeger
2005-05-15 19:46 ` Eli Zaretskii
2005-05-15 20:16 ` Joseph S. Myers
2005-05-15 22:09 ` Eli Zaretskii
2005-05-15 22:05 ` Andreas Jaeger
2005-05-16 1:24 ` Eli Zaretskii
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='01c55862$Blat.v2.4$44a795c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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