Bug#352139: getopt optional arg does not work as documented

2007-03-06 Thread Helmut Grohne
tag 352139 -wontfix reassign 352139 manpages-dev thanks > Now. This case is difficult. The string "hello" could also be just a > normal filename argument. I think the glibc handles this case correctly > and thus mark the bug as wontfix. Actually it would be even better if the documentation could

Bug#352139: getopt optional arg does not work as documented

2007-02-27 Thread Helmut Grohne
tag 352139 wontfix thanks > However, this does not seem to be the case. Actually it works quite similar. > When run: > [EMAIL PROTECTED]:/tmp$ a.out -a > a arg is: (null) Correct behaviour. $ ./a.out -afoo a arg is: foo > [EMAIL PROTECTED]:/tmp$ a.out -a hello > a arg is: (null) N

Bug#352139: getopt optional arg does not work as documented

2006-02-09 Thread Troy Heber
Package: glibc Severity: normal On sid with libc 2.3.5-13 the getopt man page states: Two colons mean an option takes an optional arg; if there is text in the current argv-element, it is returned in optarg, otherwise optarg is set to zero. This is a GNU extension. However, this does not