Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3FEFDE5B.3000801@helixdigital.com> Date: Sun, 28 Dec 2003 23:57:15 -0800 From: Dario Alcocer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 MIME-Version: 1.0 To: Peter Seebach Cc: cygwin@cygwin.com Subject: Re: Question about ash and getopts References: <200312290512.hBT5C5qd004034@guild.plethora.net> In-Reply-To: <200312290512.hBT5C5qd004034@guild.plethora.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Peter Seebach wrote: >I know this is a pseudo-FAQ, but I haven't been able to find a clear enough >answer in the archives. > >1. Is it not the case that POSIX provides a specification for the getopts >builtin? >2. Doesn't ash, as originally written, implement getopts? > >I'm trying to figure out why this feature was removed, and I've never gotten >an answer that made much sense. Every other POSIX-like system I can think >of supports getopts in /bin/sh. Why is Cygwin different? > > Use the "set -- `getopt`" idiom instead: http://cygwin.com/ml/cygwin/2003-05/msg01114.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/