Linux Manual Pages development
 help / color / mirror / Atom feed
From: Thomas Jarosch <thomas.jarosch-XXsH3GEs1jrby3iVrkZq2A@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@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: Fri, 01 Feb 2013 10:43:21 +0100	[thread overview]
Message-ID: <2211833.tieGgo36jp@storm> (raw)
In-Reply-To: <201301291344.29011.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

Hi Mike,

On Tuesday, 29. January 2013 13:44:28 you wrote:
> 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

I first added it there and then thought it's too prominent.
The "NOTES" section seemed like a better place.

Let's see if it gets accepted at all.

Thomas

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-02-01  9:43 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
     [not found]   ` <201301291344.29011.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2013-02-01  9:43     ` Thomas Jarosch [this message]
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=2211833.tieGgo36jp@storm \
    --to=thomas.jarosch-xxsh3ges1jrby3ivrkzq2a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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