Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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 16:29:47 -0500
From:	Chris Morgan <chrismorgan AT rcn DOT com>
Subject:	getopt_long behavior
To:	cygwin AT cygwin DOT com
Reply-To:	cmorgan AT alum DOT wpi DOT edu
MIME-Version:	1.0
Message-Id:	<E18dzmF-0002Lr-00@smtp03.mrf.mail.rcn.net>

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?  Is there still no plan to
switch this behavior back?  I can't imagine I'm the only one
that wishes reordering was supported.

Thanks,
Chris


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.

cgf

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

- Raw text -