Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <027601c35cf6$cf4ee430$897c883e@starfruit> From: "Max Bowsher" To: "Patrick Eisenacher" , References: <3F2F92F4 DOT 7030906 AT fillmore-labs DOT com> <025d01c35b48$33c5cd80$017c883e AT starfruit> <3F2FA3A2 DOT 5030706 AT fillmore-labs DOT com> Subject: Re: getopt & output reordering Date: Thu, 7 Aug 2003 15:38:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Patrick Eisenacher wrote: > Hi Max, > > thanks for your quick response. Indeed, setting the > POSIXLY_INCORRECT_GETOPT environment variable did the trick and produces > a result that is in synch with the man page. > > Since I don't know anything about the various flavours of getopts around > and what is posixly correct and what not, and I guess a lot of other > users don't know neither, how about updating the man pages to be in > synch with the current behaviour and adding a paragraph on the > POSIXLY_INCORRECT_GETOPT stuff? PTC. Given this: >> ... because getopt is statically linked, this only works for >> programs rebuilt since this change was made, and many haven't been yet. such a patch is unlikely to be commited until after 1.5 has been released, as most stuff will have been recompiled by then. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/