On Wed, Mar 7, 2012 at 11:21 AM, Regid Ichira <regi...@yahoo.com> wrote: > --- On Tue, 3/6/12, Michael Kerrisk (man-pages) wrote: > >> Hi. Upstream maintainer of man-pages here. I'm not at all sure that >> the problem in #655685 is because of getopt(). (How did you conclude >> that it is?) >> > > The Debian maintainer think so. Based on what is written at > http://bugs.debian.org/655685, I think it is unlikely not to point > to getopt. > >> Allowing a space between option character and argument is >> longstanding >> UNIX (and Linux behavior), and as far as I can see POSIX is >> explicit >> in allowing it > > I was just trying to make the manual page accurately document > the actual behavior of the program. Do you think I should close > my report, and file a bug to libc (assuming this is not yet > reported)?
I would say that it's a bit of a leap from reading that bug report to assume that the problem *must* be in getopt(3). I'd want to see a minimal test case demonstrating the behavior. And I assume the libc maintainers would want to see the same. In the meantime, I doubt that the problem is getopt(3), since then there would have been a rash of bug reports on this issue. -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Author of "The Linux Programming Interface"; http://man7.org/tlpi/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
