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
Message-ID: <3D160BEE.6030503@ece.gatech.edu>
Date: Sun, 23 Jun 2002 13:57:02 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: release schedule and a problem on getopt_long.
References: <s1sn0tmh9e5 DOT fsf AT jaist DOT ac DOT jp> <3D15609F DOT 2060403 AT ece DOT gatech DOT edu> <20020623055037 DOT GA3955 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sure enough:
http://www.cygwin.com/ml/cygwin-developers/2001-09/msg00414.html

But apparently the decision was reached to force POSIXLY_CORRECT in 
order to enable strace (and others) to work as the did before the GNU 
getopt.c was included.  However, the decision itself was not reflected 
in the archive -- except perhaps in cygwin-cvs <g>.  You were, at that 
time, "inclined to leave it the way it is" -- e.g. normal GNU behavior, 
with POSIXLY_CORRECT defaulting to off, and responsive to the 
environment variable of the same name -- but it appears that you changed 
your mind.

As I said, it's not really a problem and is easy enough to work around. 
  Thanks for the pointer.

--Chuck

Christopher Faylor wrote:

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