This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug faq/1395] New: canonicalize_file_name documentation typos
- From: "oskar at osk dot mine dot nu" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 30 Sep 2005 09:19:25 -0000
- Subject: [Bug faq/1395] New: canonicalize_file_name documentation typos
- Reply-to: sourceware-bugzilla at sourceware dot org
There's a small typo in the texinfo documentation for
canonicalize_file_name. Perhaps there's also an incorrect
statement which indirectly says that it is OK for the last path
component to be missing. I don't think this is true.
The comment for realpath in stdlib/canonicalize.c also states
"All path components must exist".
Oskar Liljeblad (oskar@osk.mine.nu)
diff -u filesys.texi.v0 filesys.texi
--- filesys.texi.v0 2005-09-30 11:11:01.000000000 +0200
+++ filesys.texi 2005-09-30 11:11:25.000000000 +0200
@@ -1199,7 +1199,7 @@
memory allocated with @code{malloc}. If the result is not used anymore
the memory should be freed with a call to @code{free}.
-In any of the path components except the last one is missing the
+If any of the path components is missing the
function returns a NULL pointer. This is also what is returned if the
length of the path reaches or exceeds @code{PATH_MAX} characters. In
any case @code{errno} is set accordingly.
--
Summary: canonicalize_file_name documentation typos
Product: glibc
Version: 2.3.5
Status: NEW
Severity: normal
Priority: P2
Component: faq
AssignedTo: aj at suse dot de
ReportedBy: oskar at osk dot mine dot nu
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=1395
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.