Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <000601be6f47$f7bc0c50$e53b4ec6@hunda>
From: "Suhaib M. Siddiqi" <Ssiddiqi AT InspirePharm DOT Com>
To: <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: MKS Tool kit copies request
Date: Mon, 15 Mar 1999 19:57:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3



>> From: Jason Zions <jason_zions AT interix DOT 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 AT sourceware DOT cygnus DOT com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com