linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Jeff Mahovsky <Jeff.Mahovsky-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: stat(2) does not indicate behavior with NULL filename arg, man pages 3.24
Date: Mon, 24 May 2010 07:23:00 +0200	[thread overview]
Message-ID: <AANLkTinqBaEquWOSvaFBEosJ2Fritb2D3h6YVbosFfVk@mail.gmail.com> (raw)
In-Reply-To: <4BCF4B3A.8020909-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org>

Jeff

On Wed, Apr 21, 2010 at 9:00 PM, Jeff Mahovsky
<Jeff.Mahovsky-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org> wrote:
> The stat(2) manpage does not indicate the behavior of the stat() function
> when the filename is a NULL pointer.  Does stat() return an error or is the
> behavior undefined?
>
> Jeff Mahovsky
> Dreamworks Animation

Just to add to what Petr said. A NULL pointer is a general kind of
error that can affect many interfaces. I don't really see a need to
document this case for a specific interface.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
--
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:[~2010-05-24  5:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 19:00 stat(2) does not indicate behavior with NULL filename arg, man pages 3.24 Jeff Mahovsky
     [not found] ` <4BCF4B3A.8020909-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org>
2010-05-11  1:46   ` Petr Baudis
2010-05-24  5:23   ` Michael Kerrisk [this message]

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=AANLkTinqBaEquWOSvaFBEosJ2Fritb2D3h6YVbosFfVk@mail.gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=Jeff.Mahovsky-hCDZnVt6e3JSwrhanM7KvQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pasky-AlSwsSmVLrQ@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).