Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sat, 22 Sep 2001 20:19:28 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: New getopt.c has different behavior -- should it? Message-ID: <20010922201928.A21633@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i The new getopt.c that I just added to winsup/cygwin/lib exhibts different, more GNU-like behavior when it parses arguments. I noticed the difference when I did this: strace -om:/tmp/strace.out ls -l and strace complained that it didn't have an option '-l'. So, I tried this: strace -om:/tmp/strace.out -- ls -l and got the expected behavior. You can work around this behavior by setting the POSIXLY_CORRECT environment variable. So, the question is, which way *should* it be? I'm inclined to leave it the way it is, since it seems to be more gnu-like but I don't want to cause people problems or generate unnecessary cygwin email traffic. cgf