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 Date: Wed, 29 Jan 2003 20:00:56 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: getopt_long behavior Message-ID: <20030130010056.GA3603@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Wed, Jan 29, 2003 at 04:29:47PM -0500, Chris Morgan wrote: >I orginally posted this message some time ago. Having all of >the cygwin tools lacking the ability to accept arguments in >arbirtary order makes it more difficult to use them(I often do >grep "string" *.c and then rerun with -i at the end). Is >there anyway to get around this without recompiling the whole >cygwin suite from source code? No. >On Thu, Sep 05, 2002 at 04:52:01AM -0400, chrismorgan AT rcn DOT com >wrote: >>I noticed that getopt() and getopt_long() aren't doing reordering of >>argv entries. Searching the cygwin-developers mailing list I found >>that this is due to compiling with POSIXLY_CORRECT set. Is there any >>plan to move back to not setting this variable? > >No. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/