Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 11 Oct 2000 10:14:22 -0400
From:	Chet Ramey <chet AT nike DOT ins DOT cwru DOT edu>
To:	dj AT delorie DOT com
Subject:	Re: getopts missing with latest cygwin
Cc:	cygwin AT sourceware DOT cygnus DOT com
Reply-To:	chet AT po DOT CWRU DOT Edu
Message-ID:	<1001011141422.AA92545.SM@nike.ins.cwru.edu>
Read-Receipt-To:	chet AT po DOT CWRU DOT Edu
MIME-Version:	1.0
X-In-Reply-To:	Message from dj AT delorie DOT com of Tue, 10 Oct 2000 18:12:38 -0400 (id <200010102212 DOT SAA13461 AT envy DOT delorie DOT com>)

> > Worse than useless :-)
> 
> Sigh, I guess I'm just going to have to respond with hard proof, since
> everyone who's saying "it can't work!" never bothered to find out what
> that kind of program really does.

You're confusing getopt(1), which appears in SVR2-based systems, and
getopts(1), the subject of this discussion.

Your description of getopt(1) is correct, but not really relevant.  That
program has problems of its own, like quoting arguments containing
whitespace.  That issue, and others, is what inspired the implementation
of getopts(1), which first appeared in the SVR3 sh.




-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, CWRU    chet AT po DOT CWRU DOT Edu    http://cnswww.cns.cwru.edu/~chet/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -