Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<200312290512.hBT5C5qd004034@guild.plethora.net>
From:	seebs AT plethora DOT net (Peter Seebach)
To:	cygwin AT cygwin DOT com
Reply-To:	seebs AT plethora DOT net (Peter Seebach)
Subject:	Question about ash and getopts
Date:	Sun, 28 Dec 2003 23:12:05 -0600
X-IsSubscribed:	yes

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
builtin?
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?

-s

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -