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
Message-ID: <001301c2c7e8$11fb57e0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <E18dzmF-0002Lr-00 AT smtp03 DOT mrf DOT mail DOT rcn DOT net>
Subject: Re: getopt_long behavior
Date: Wed, 29 Jan 2003 22:45:06 -0000
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.1106

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

No, me too. I guess CGF has his reasons.

However, since that change has the log message...
* select.cc (peek_pipe): Only grab mutex when we actually got something from
the pipe.... it is pretty hard to guess what they might be.Chris (Faylor):
Is there any chance of convincing you to revert this? If not, could you
mention why you did it, so we don't suffer in ignorance, and would you
accept a patch making getopt respond to a "POSIXLY_INCORRECT_GETOPT" envvar?
Max.


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