Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!killer!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!lvc
From: lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani)
Newsgroups: comp.unix.wizards
Subject: Re: ksh incompatabilities with sh?
Summary: incompatibilities in ksh book
Message-ID: <14123@tut.cis.ohio-state.edu>
Date: 24 May 88 19:46:16 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <4402@vdsvax.steinmetz.ge.com> <54188@sun.uucp>
Organization: Ohio State Computer & Info Science
Lines: 19

In article <54188@sun.uucp>, guy@gorodish.Sun.COM (Guy Harris) writes:
< > > Well, no, you really can't, not always.  There are supposedly a few real
< > > live incompatibilities that may break some scripts.
< > 
< > I have heard this too, over the years, and would like real
< > documentation on what's wrong.
<
<	anecdote of someones experience replacing sh with ksh removed
< 
< The Korn shell (the pre-"ksh-i" version, anyway) does come with a file named
< COMPATIBILITY that lists a number of "sh"/"ksh" incompatibilities.

The book (still unpublished) by Korn and Bolsky on ksh programming has
an appendix that lists all the incompatibilities between ksh and SVR2 sh.

-- 
Larry Cipriani, AT&T Network Systems and Ohio State University
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (weird but right)