Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 11 Oct 2000 10:14:22 -0400 From: Chet Ramey To: dj@delorie.com Subject: Re: getopts missing with latest cygwin Cc: cygwin@sourceware.cygnus.com Reply-To: chet@po.CWRU.Edu Message-ID: <1001011141422.AA92545.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from dj@delorie.com of Tue, 10 Oct 2000 18:12:38 -0400 (id <200010102212.SAA13461@envy.delorie.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@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com