In message <[EMAIL PROTECTED]>, Larry Hall writes: >OK, sounds to me like you've convinced yourself that ash should contain >getopts. Does that mean that you no longer have a need to keep this thread >going? I'm not sure I see the discussion providing any useful benefit beyond >you becoming more comfortable with your original position. If I'm wrong, >please show us where you're headed. If not and your main goal was to just >point out that ash doesn't have getopts, then let's end the thread. There's >little point to covering the same ground on this topic again.
The goal here is that I would like Cygwin to be the best environment it could be, since I use it, and I sometimes want to recommend such an environment to people, and I dislike having to say "it's very much like Unix, except that standard POSIX shell scripts that have worked on every Unix system anywhere since the late 80's won't run on it". In short, I think this mistake should be recognized as just that - a mistaken devotion to the Little Tin God - and corrected. Then Cygwin will be one obvious step closer to POSIX compliance, and there will no longer be periodic repititions of the question "why doesn't my POSIX-compliant shell script work with this /bin/sh", followed quickly by the question "why did someone put special effort into breaking it". This has already made its way into a book as an example of false efficiency. -s -- 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/
