This is the mail archive of the
mailing list for the Cygwin project.
Re: Question about ash and getopts
- From: seebs at plethora dot net (Peter Seebach)
- To: cygwin at cygwin dot com
- Date: Mon, 29 Dec 2003 02:07:23 -0600
- Subject: Re: Question about ash and getopts
- Reply-to: seebs at plethora dot net (Peter Seebach)
In message <3FEFDE5B.firstname.lastname@example.org>, Dario Alcocer writes:
>Peter Seebach wrote:
>>I know this is a pseudo-FAQ, but I haven't been able to find a clear enough
>>answer in the archives.
>>1. Is it not the case that POSIX provides a specification for the getopts
>>2. Doesn't ash, as originally written, implement getopts?
>>I'm trying to figure out why this feature was removed, and I've never gotten
>>an answer that made much sense. Every other POSIX-like system I can think
>>of supports getopts in /bin/sh. Why is Cygwin different?
>Use the "set -- `getopt`" idiom instead:
Yes, but *why*? Why not use the thing that's in the POSIX shell spec,
which works everywhere else?
I have a few dozen scripts which have worked on every Unix system I've seen
since the mid-90s, and the feature appears to date back to SVR3 (1986).
I could understand not implementing it; what I can't understand is expending
extra effort to remove it.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html