tags 516293 fixed-upstream thanks On 2/21/09, Reuben Thomas <[email protected]> wrote: > Package: manpages-dev > Version: 3.05-1 > Severity: normal > > > The BUGS section starts with a bald "Avoid using this function", but > that advice only applies to calls with a non-NULL second argument. If > one uses the glibc extension (which the POSIX man page hints may well > become standard) then one is safe. Hence, the advice should be more > like: "Avoid using this function with a non-NULL second argument, for > the reasons explained below. Passing NULL as the second argument is a > non-POSIX use, so is non-portable."
Hello Reuben, In fact, the story is even a little better than you realize, since POSIX.1-2008 already standardized the resolved_path==NULL feature. The man page had already been updated to reflect that fact, but still the sentence that you pointed out remained in BUGS. I've removed that sentence, and recast the discussion in terms of "The POSIX.1-2001 version of the function is broken by design, since... The resolved_path==NULL feature, standardized in POSIX.1-2008, addresses this design problem." The changes will be in man-pages-3.20. Cheers, Michael > -- System Information: > Debian Release: 5.0 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages manpages-dev depends on: > ii manpages 3.05-1 Manual pages about using a > GNU/Lin > > manpages-dev recommends no packages. > > Versions of packages manpages-dev suggests: > ii man-db [man-browser] 2.5.2-4 on-line manual pager > > -- no debconf information > > > > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
