public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "madcoder at debian dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/4368] New: bad documentation in stdlib.h
Date: Sun, 15 Apr 2007 15:44:00 -0000	[thread overview]
Message-ID: <20070415164444.4368.madcoder@debian.org> (raw)

in stdlib.h we read:

/* Return the canonical absolute name of file NAME.  The last file name 
   component need not exist, and may be a symlink to a nonexistent file. 
   If RESOLVED is null, the result is malloc'd; otherwise, if the canonical 
   name is PATH_MAX chars or more, returns null with `errno' set to 
   ENAMETOOLONG; if the name fits in fewer than PATH_MAX chars, returns the 
   name in RESOLVED.  */ 
extern char *realpath (__const char *__restrict __name, 
                       char *__restrict __resolved) __THROW __wur; 



the part about "The last file name component need not exist, and may be a 
symlink to a nonexistent file" is wrong twice as:
 * it does not describe how the libc performs ;
 * it does not conforms to POSIX either.

I suggest this sentence to be removed from stdlib.h.

-- 
           Summary: bad documentation in stdlib.h
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: madcoder at debian dot org
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4368

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-04-15 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 15:44 madcoder at debian dot org [this message]
2007-04-17 18:36 ` [Bug libc/4368] " drepper at redhat dot com
2007-07-12 15:10 ` cvs-commit at gcc dot gnu dot org

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=20070415164444.4368.madcoder@debian.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).