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: <29950-22003132922425749@M2W092.mail2web.com> X-Priority: 3 Reply-To: lhall AT rfk DOT com X-Originating-IP: 209.113.174.244 From: "lhall AT pop DOT ma DOT ultranet DOT com" To: cmorgan AT alum DOT wpi DOT edu, cygwin AT cygwin DOT com Subject: RE: getopt_long behavior Date: Wed, 29 Jan 2003 17:42:57 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 29 Jan 2003 22:42:57.0154 (UTC) FILETIME=[C4B7AE20:01C2C7E7] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h0TMhAe10617 Giving the impression that ordering of arguments is not significant is not a good idea in general. Although what you're looking for is an extreme, the fact that you can generally interchange the order of flags ( grep -i -c *.c vs grep -c -i *.c) does generate expectations for all tools. This uniformity isn't going to be met by all tools (like gcc and linker flags). So adding to the flexibility as you suggest would only tend to increase the inquiries and problems folks currently have for these kinds of tools. I don't think it's wise to look at making any tool accept any argument in any order. I expect you'd find this isn't practical anyway. But, that's just my opinion and it ain't worth much! ;-) Reasonably speaking, Cygwin targets POSIX compatibility. For better or worse, conforming to this standard comes with certain restrictions on behavior. I can only offer the consolation that at least since Cygwin is open-source, you have the option to build it the way you want it, if you want it bad enough. ;-) Larry Original Message: ----------------- From: Chris Morgan chrismorgan AT rcn DOT com Date: Wed, 29 Jan 2003 16:29:47 -0500 To: cygwin AT cygwin DOT com Subject: getopt_long behavior 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/ -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . -- 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/