public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3460] New: canonicalize_file_name comment is wrong Date: Mon, 06 Nov 2006 14:40:00 -0000 [thread overview] Message-ID: <20061106144029.3460.bruno@clisp.org> (raw) The description of canonicalize_file_name in <stdlib.h> does not match the behaviour of the canonicalize_file_name function. Here is a patch that clarifies that it behaves like gnulib's "canonicalize_filename_mode (name, CAN_EXISTING)". *** stdlib/stdlib.h.bak 2006-01-24 20:38:08.000000000 +0100 --- stdlib/stdlib.h 2006-11-06 15:29:24.000000000 +0100 *************** *** 741,748 **** #ifdef __USE_GNU /* Return a malloc'd string containing the canonical absolute name of the ! named file. The last file name component need not exist, and may be a ! symlink to a nonexistent file. */ extern char *canonicalize_file_name (__const char *__name) __THROW __nonnull ((1)) __wur; #endif --- 741,748 ---- #ifdef __USE_GNU /* Return a malloc'd string containing the canonical absolute name of the ! named file. If any file name component does not exist or is a symlink ! to a nonexistent file, return NULL. */ extern char *canonicalize_file_name (__const char *__name) __THROW __nonnull ((1)) __wur; #endif Btw, the bug tracker does not allow me to enter "Version: 2.5", but glibc-2.5 is already released. -- Summary: canonicalize_file_name comment is wrong Product: glibc Version: 2.4 Status: NEW Severity: minor Priority: P3 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: bruno at clisp dot org CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=3460 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-11-06 14:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-06 14:40 bruno at clisp dot org [this message] 2006-11-06 15:57 ` [Bug libc/3460] " drepper at redhat dot com
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=20061106144029.3460.bruno@clisp.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: linkBe 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).