src/lib/libc/stdlib/getopt.c, branch release/6.0.0_cvs FreeBSD source tree This commit was manufactured by cvs2svn to create tag 2005-11-03T00:35:26+00:00 cvs2svn cvs2svn@FreeBSD.org 2005-11-03T00:35:26+00:00 3640cb54210edbb7edbf1b12ef0127ecfcea967d 'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image. 
'RELENG_6_0_0_RELEASE'.

This commit was manufactured to restore the state of the 6.0-RELEASE image.
Merge some fixes from NetBSD's getopt.c v1.26: 2004-03-06T17:05:45+00:00 Andrey A. Chernov ache@FreeBSD.org 2004-03-06T17:05:45+00:00 9109761318efa6644bdfeea7c47421cdad6338d2 cleanups, handling 'ls -l-', handling '--*' Note this is in the same time back out of our v1.3 "Don't print an error message if the bad option is '?'" because it directly violates POSIX. 
cleanups, handling 'ls -l-', handling '--*'

Note this is in the same time back out of our v1.3
"Don't print an error message if the bad option is '?'"
because it directly violates POSIX.
Do not use __progname directly (except in [gs]etprogname(3)). 2002-03-29T22:43:43+00:00 Mark Murray markm@FreeBSD.org 2002-03-29T22:43:43+00:00 4cd01193678a79d81b61be31c50b139d7a4c44d4 Also, make an internal _getprogname() that is used only inside libc. For libc, getprogname(3) is a weak symbol in case a function of the same name is defined in userland. 
Also, make an internal _getprogname() that is used only inside
libc. For libc, getprogname(3) is a weak symbol in case a
function of the same name is defined in userland.
Fix the style of the SCM ID's. 2002-03-22T21:53:29+00:00 David E. O'Brien obrien@FreeBSD.org 2002-03-22T21:53:29+00:00 333fc21e3cd79bca0c94d7722c5a56cb5ad078d1 I believe have made all of libc .c's as consistent as possible. 
I believe have made all of libc .c's as consistent as possible.
If the string specifying the allowed options starts with a leading `:', 2001-08-16T03:27:03+00:00 Joseph Koshy jkoshy@FreeBSD.org 2001-08-16T03:27:03+00:00 2f46ebcdb7c6e5ea0cee3237188982d0df88c8a9 `getopt(3)' should not print a warning for missing argument values. PR: bin/29625 Reviewed by: mikeh MFC after: 1 week 
`getopt(3)' should not print a warning for missing argument values.

PR:		bin/29625
Reviewed by:	mikeh
MFC after:	1 week
Don't print an error message if the bad option is '?'. This has been 2000-09-04T03:49:22+00:00 Warner Losh imp@FreeBSD.org 2000-09-04T03:49:22+00:00 e9d918edb6b393ade32620c1625be0a2bd77beef in my tree for a long time. bde reviewed this once upon a time and said it was OK, iirc. This also obviates the need to put ? in the optstring argument to preclude the extra warning message which some people think confuses users. When I made my getopt cleanups of a long time ago, this was the compromise reached. I just neglected to commit it until now. 
in my tree for a long time.  bde reviewed this once upon a time and
said it was OK, iirc.  This also obviates the need to put ? in the
optstring argument to preclude the extra warning message which some
people think confuses users.  When I made my getopt cleanups of a long
time ago, this was the compromise reached.  I just neglected to commit
it until now.
Fix handling of trailing :'s to match what other OSes do (spit out 1999-12-17T01:52:15+00:00 Jordan K. Hubbard jkh@FreeBSD.org 1999-12-17T01:52:15+00:00 f8d7aff7a07dde61ac0faf4dc01187b288107e81 a diagnostis). Submitted by: Guy Harris <gharris@flashcom.net> 
a diagnostis).

Submitted by:	Guy Harris <gharris@flashcom.net>
Import CSRG 4.4BSD-Lite2 lib/libc onto vendor branch 1997-03-11T11:29:42+00:00 Peter Wemm peter@FreeBSD.org 1997-03-11T11:29:42+00:00 662909a7800d5634772b89ca1509765dda837508