linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Thomas Jarosch <thomas.jarosch-XXsH3GEs1jrby3iVrkZq2A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [man-pages PATCH] Add note about calling fclose(NULL)
Date: Tue, 29 Jan 2013 13:44:28 -0500	[thread overview]
Message-ID: <201301291344.29011.vapier@gentoo.org> (raw)
In-Reply-To: <1695270.M7m4ekngnN@storm>

[-- Attachment #1: Type: Text/Plain, Size: 439 bytes --]

On Tuesday 29 January 2013 11:24:43 Thomas Jarosch wrote:
> --- a/man3/fclose.3
> +++ b/man3/fclose.3
> @@ -97,6 +97,10 @@ on disk the kernel buffers must be flushed too, for
> example, with .BR sync (2)
>  or
>  .BR fsync (2).
> +Also it's undefined behavior to call
> +.BR fclose ()
> +with a NULL pointer.
> +
>  .SH "SEE ALSO"
>  .BR close (2),
>  .BR fcloseall (3),

i wonder if it'd be better placed in the DESCRIPTION section
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-29 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 16:24 [man-pages PATCH] Add note about calling fclose(NULL) Thomas Jarosch
2013-01-29 18:44 ` Mike Frysinger [this message]
     [not found]   ` <201301291344.29011.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2013-02-01  9:43     ` Thomas Jarosch
2013-02-02  9:35       ` Mike Frysinger
2013-01-31  0:50 ` Michael Kerrisk (man-pages)
     [not found]   ` <CAKgNAkiQsWWWTfLWeixN5+GcwkfP6UX+AYdL4HY6beq7rdpUxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-31  8:26     ` Thomas Jarosch
2013-02-02  1:11       ` Michael Kerrisk

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=201301291344.29011.vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=thomas.jarosch-XXsH3GEs1jrby3iVrkZq2A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).