diff options
author | Denis Vlasenko | 2008-11-09 17:21:26 +0000 |
---|---|---|
committer | Denis Vlasenko | 2008-11-09 17:21:26 +0000 |
commit | 84641942e5366b2e09367ba4f4376c99f15ecc8e (patch) | |
tree | eff2511dcc6cb647e0bf898903f86c94b85466ad /libbb/getopt32.c | |
parent | bacaff6e5474d6c5f080ce4cd2a55e8ff1ba5c94 (diff) | |
download | busybox-84641942e5366b2e09367ba4f4376c99f15ecc8e.zip busybox-84641942e5366b2e09367ba4f4376c99f15ecc8e.tar.gz |
apply post-1.12.1 patches, bump version to 1.12.21_12_2
Diffstat (limited to 'libbb/getopt32.c')
-rw-r--r-- | libbb/getopt32.c | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/libbb/getopt32.c b/libbb/getopt32.c index 8fb99b6..ee85181 100644 --- a/libbb/getopt32.c +++ b/libbb/getopt32.c @@ -515,28 +515,6 @@ getopt32(char **argv, const char *applet_opts, ...) } } - /* In case getopt32 was already called: - * reset the libc getopt() function, which keeps internal state. - * - * BSD-derived getopt() functions require that optind be set to 1 in - * order to reset getopt() state. This used to be generally accepted - * way of resetting getopt(). However, glibc's getopt() - * has additional getopt() state beyond optind, and requires that - * optind be set to zero to reset its state. So the unfortunate state of - * affairs is that BSD-derived versions of getopt() misbehave if - * optind is set to 0 in order to reset getopt(), and glibc's getopt() - * will core dump if optind is set 1 in order to reset getopt(). - * - * More modern versions of BSD require that optreset be set to 1 in - * order to reset getopt(). Sigh. Standards, anyone? - */ -#ifdef __GLIBC__ - optind = 0; -#else /* BSD style */ - optind = 1; - /* optreset = 1; */ -#endif - /* optarg = NULL; opterr = 0; optopt = 0; - do we need this?? */ pargv = NULL; /* Note: just "getopt() <= 0" will not work well for |