This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: MKS Tool kit copies request
- To: <cygwin@sourceware.cygnus.com>
- Subject: Re: MKS Tool kit copies request
- From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
- Date: Mon, 15 Mar 1999 19:57:28 -0500
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
>> From: Jason Zions <jason_zions@interix.com>
>>
>> As for Dave Korn claiming that only U/WIN has a "real" KornShell, this
>
>I'm not sure he's ever claimed this. He did point out to MS that
>the version they plan to ship isn't very compatible with most
>current implementations.
>
Yes he had claimed that on a few occasions on U/WIN users mailing list, a
while ago.
>I've never heard Korn speak on the subject, so I've no idea if this
>reasonably reflects his views. The Korn shell has been standardized,
>in XPG4 at least if not POSIX, and the version marketed by MKS has
>long had the reputation of being about the least compatible Korn
>shell available on any platform. I've never used it, I've no idea
>how accurate that characterization was back then, and I don't know if
>they've brought it more closely into line since it was standardized.
>
Ksh in MKS Tool kit's ksh is not bad for normal scripting tasks. Most of
the ksh features are implemented, at least all the standards.
>Why pay money for a commercial product with a poor reputation when
>pdksh is available?
>
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com