Xref: utzoo comp.unix.questions:6880 comp.unix.wizards:8276
Path: utzoo!mnetor!uunet!husc6!im4u!tut.cis.ohio-state.edu!bloom-beacon!mgm.mit.edu!wolfgang
From: wolfgang@mgm.mit.edu (Wolfgang Rupprecht)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: KSH portability
Message-ID: <5146@bloom-beacon.MIT.EDU>
Date: 6 May 88 04:19:11 GMT
References: <295@cmtl01.UUCP> <12142@tut.cis.ohio-state.edu> <631@vsi.UUCP> <4063@mtgzz.UUCP> <52159@sun.uucp>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wolfgang@mgm.mit.edu (Wolfgang Rupprecht)
Organization: Freelance Software Consultant, Boston, Ma.
Lines: 15

In article <52159@sun.uucp> guy@gorodish.Sun.COM (Guy Harris) writes:
>	3) The previous version assumed that the "_iob" structures for standard
>	   I/O were in one long contiguous block.  The 4.3BSD standard I/O
>	   library puts the first 30 or so into such a block, and "malloc"s
>	   additional ones.

Ksh and Kcl (Kyoto Common Lisp) both have/had problems with assuming
that all _iob's are always contigious.  What *is* the "approved"
method of finding all _iob's?  I have used the internal 4.3BSD libc
function findiop:_fwalk(function) to walk over and close all but the
first 3 _iob's.  Is there *legit* way to do this?
---
Wolfgang Rupprecht	ARPA:  wolfgang@mgm.mit.edu (IP 18.82.0.114)
326 Commonwealth Ave.	UUCP:  mit-eddie!mgm.mit.edu!wolfgang
Boston, Ma. 02115	TEL:   (617) 267-4365