openbsd/src/lib/libc/stdlib/getopt_long.c, branch pre_openssl_0_9_8h A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=pre_openssl_0_9_8h 2008-07-28T23:44:12+00:00 This commit was manufactured by cvs2git to create tag 'pre_openssl_0_9_8h'. 2008-07-28T23:44:12+00:00 cvs2svn admin@example.com 2008-07-28T23:44:12+00:00 urn:sha1:daac2f633f49a45baa8412c5e4e71e594236e7b8 Add parentheses to avoid warning: 2007-10-31T12:34:57+00:00 chl 2007-10-31T12:34:57+00:00 urn:sha1:39f521b345b60e52d3e0004a5da2b8405ffe8669 "suggest parentheses around && within ||" ok millert@ from wiz@netbsd: 2006-10-04T21:29:04+00:00 jmc 2006-10-04T21:29:04+00:00 urn:sha1:ccdc6ac975add328efc7bcfa904dd3157dba2625 Log Message: Switch from 4-clause to 2-clause BSD license. Ok dillo@, board@. Back out change in rev 1.15 of to allow whitespace to separate a 2006-09-22T17:22:05+00:00 millert 2006-09-22T17:22:05+00:00 urn:sha1:6ea1c04e14cde761e2faac093669b503a7965de7 flag from its optional argument if permutation is disabled. The idea was that since "r:" would match "-r foo" then "r::" should match "-r foo" too as long as we know that things have not been reshuffled. Unfortunately, this causes incompatibilities with GNU getopt_long when the POSIXLY_CORRECT environment variable is set. OK deraadt@ dont' -> don't in comments; 2005-10-25T15:49:37+00:00 jmc 2005-10-25T15:49:37+00:00 urn:sha1:e3931da1c5e17a3f0017666ac693b6252f746993 from ray lai; zap remaining rcsid. 2005-08-08T08:05:37+00:00 espie 2005-08-08T08:05:37+00:00 urn:sha1:d7398a270c9cd1b7b4d545ed70ea24384781a86c Kill old files that are no longer compiled. okay theo ansi + de-register 2005-03-30T18:51:49+00:00 pat 2005-03-30T18:51:49+00:00 urn:sha1:894b6ab0099e7d9ca2ad9acb75246cd0a4542167 ok otto deraadt An optional argument cannot start with '-', even if permutation is 2004-06-03T18:46:52+00:00 millert 2004-06-03T18:46:52+00:00 urn:sha1:bea8674d8fa57fb3227fdc5b14c3af3a00d97a20 disabled. Magne Oestlyngen. Traditionally, getopt(3) has treated "--foo" the same as "--". However, 2004-02-04T18:17:25+00:00 millert 2004-02-04T18:17:25+00:00 urn:sha1:b5f1b51f776a16e2dfaf65d9bb74fbc361a8e032 this can cause confusion when a user tries to use a long option with a program that only supports short options. Furthermore, it appears to be in violation of POSIX, which states that "--" shall indicate the end of argument processing, not any string that begins with "--". OK otto@ and closes PR 3666. If permutation is disabled (as it is via getopt(3) or when POSIXLY_CORRECT 2003-09-22T23:45:22+00:00 millert 2003-09-22T23:45:22+00:00 urn:sha1:fb596a0bc3c3e40564f75af219aaf48a059a9b32 is set), we can accept an optional arg separated by whitespace. Previously, the optional arg needed to be adjacent to the option character. deraadt@ OK