Mail Archives: cygwin/2000/10/09/20:13:45
> The "ash maintainer" is either me or Corinna. FWIW, I don't plan on
> changing this. I want ash to be small and fast when running configure
> scripts. I've stripped ash down to support only the minimal set of
> functionality found in older versions of UNIX. I use the /bin/sh on
> Digital UNIX 3.2 as a reference.
>
> If you want more functionality, use bash.
>
> FYI, getopts can also be a separate program although we don't supply it
> with cygwin, currently.
The stripped down sh makes sense for its intended purpose. However, I've
got a situation where (1) I need to parse the command line, (2) my customers
demand bourne shell scripts (no bash, csh, or ksh), and (3) the scripts must
run on Solaris and cygwin/NT. Currently I use getopts in the shell scripts
and have the NT customers copy bash.exe to sh.exe.
Of all ash's disabled features (bg, exp, let, fc, fg, getopts, jobid, jobs,
local, printf, setvar, unalias, and alias) , only getopts is found in
/bin/sh for commercial UNIX releases like SunOS/Solaris, HP/UX, SVR[3,4,5],
IRIX, and AIX. I would resist enabling features not found in standard
/bin/sh's, but getopts is standard for every AT&T and Sun derived sh since
1990.
What's the process for including the separate process getopts in the next
cygwin?
Thanks!
- Erik
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -