Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Sun, 23 Jun 2002 01:50:37 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: release schedule and a problem on getopt_long.
Message-ID:	<20020623055037.GA3955@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<s1sn0tmh9e5 DOT fsf AT jaist DOT ac DOT jp> <3D15609F DOT 2060403 AT ece DOT gatech DOT edu>
Mime-Version:	1.0
In-Reply-To:	<3D15609F.2060403@ece.gatech.edu>
User-Agent:	Mutt/1.3.23.1i

On Sun, Jun 23, 2002 at 01:46:07AM -0400, Charles Wilson wrote:
>Not really a problem; I simply linked in gettext's copy of the GNU 
>version of the getopt functions.  But. I am curious why cygwin's 
>implementation forces POSIXLY_CORRECT.  Anybody know?

I seem to recall that I did this to force similar behavior with the
previous version of cygwin's getopt.  There may even be a discussion
about this in the archives somewhere.

cgf

- Raw text -