Xref: utzoo comp.unix.questions:6868 comp.unix.wizards:8259
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!athena.mit.edu!wesommer
From: wesommer@athena.mit.edu (William Sommerfeld)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: KSH portability
Message-ID: <5123@bloom-beacon.MIT.EDU>
Date: 5 May 88 17:37:45 GMT
References: <295@cmtl01.UUCP> <12142@tut.cis.ohio-state.edu> <631@vsi.UUCP> <4063@mtgzz.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wesommer@athena.mit.edu (William Sommerfeld)
Organization: Massachusetts Institute of Technology
Lines: 31

In article <4063@mtgzz.UUCP> avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed) writes:
>In article <631@vsi.UUCP>, friedl@vsi.UUCP (Stephen J. Friedl) writes:
>> 
>> Note that porting ksh is not at all a task for the novice; it is
>> not (to put it politely) "maximally portable".
>
>What experience is that comment based on? 

I don't know about his experience, but I heard an interesting story
from someone at Apollo.

When they did their UNIX emulation for AEGIS, one of the things they
wrote was a version of the stdio library.  They worked from the
published interface specifications for the library (the manual pages),
not from existing source code.  As a result, their definition for what
a FILE * looked like internally was not exactly what is found in the
SysV distribution in <stdio.h>.

They put this into a release, and shipped it.

Some time later, they got an irate phone call fron Korn, who
complained that his shell didn't compile on apollos.  Why?  Portions
of ksh went "around" the published interface to stdio, and mucked with
the elements of the FILE * directly.

Apollo reluctantly re-implemented stdio with a "compatible" header
file.

Korn should have known better.

					- Bill