On Fri, May 29, 2015 at 07:50:09AM +0200, Harald van Dijk wrote: > > But the test script in this thread does invoke getopts with > parameters that are the same in all invocations, and without > modifying OPTIND. I don't see anything else in the normative > sections that would make the result undefined or unspecified either. > I do think the script is valid, and the results in dash should match > those of other shells. The bash behaviour makes it impossible to call shell functions that invoke getopts while in the middle of an getopts loop. IMHO the dash behaviour makes a lot more sense since a function always brings with it a new set of parameters. That plus the fact that this behaviour has been there since day one makes me reluctant to change it since the POSIX wording is not all that clear. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe dash" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html