release schedule and a problem on getopt_long.

[Charles Wilson]

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
>