On Mon, 19 Jun 2000, Paul Lussier wrote:
>> (Of course, bash's extensions, which I make liberal use of, aren't exactly
>> "portable", either.)
>
> That's ksh is for :)
Two questions:
Is ksh required by POSIX?
Is ksh generally implemented by all the various Unixes out there (both
commercial and free)? (POSIX conformance varies.)
I'm genuinely curious.
> Of course all shell scripting should be done in either pure /bin/sh ...
You just used "pure" and a Unix feature in the same sentence. Isn't that an
oxymoron? :-)
> ... or perl ...
I wouldn't call Perl a "shell scripting language". It's a tremendously
useful tool, but not something that should be used for critical system
functions. In particular, I really hate people who put Perl scripts in
/etc/init.d (or local equivalent). Why do people thing /usr will always be
there?
While I'm ranting (who me?), I really hate APC's PowerChute for Linux
software, which requires libstdc++ to send shutdown calls to the UPS. That
don't work too well when it is called at the end of rc.halt and /usr is
already unmounted. :-(
> (though I've heard good things about python).
I'm actually learning it in my Copious Free Time, because it seems to do
real well as a UI-independent tool for designing easy-to-use front-ends for
things. IOW, something that needs to work both as an X program and on
character terminals. The fact that whitespace is syntactically significant
kind of bothers me, but no more so then about half of the C++ or Perl features
I see used. ;-)
--
Ben Scott <[EMAIL PROTECTED]>
Net Technologies, Inc. <http://www.ntisys.com>
Voice: (800)905-3049 x18 Fax: (978)499-7839
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
