Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (A Wizard of Earth C) Subject: Re: no _iobuf in stdio.h ??? Message-ID: <1993May13.230920.9315@fcom.cc.utah.edu> Sender: news@fcom.cc.utah.edu Organization: Weber State University (Ogden, UT) References: <1993May12.234800.5360@sifon.cc.mcgill.ca> Date: Thu, 13 May 93 23:09:20 GMT Lines: 31 In article <1993May12.234800.5360@sifon.cc.mcgill.ca> storm@cs.mcgill.ca (Marc Wandschneider) writes: > > >I'm working trying to compile a rather scary ass program that was written >with a lot of assumptions about what UNIX looks like. > >One of the assumptions it made is that stdin is a record with a field >named _cnt. # of bytes read from the device/file into the FILE (stdin) buffer. This is for programs that like to dork with buffer contents. The equivalent is determined by the values of _lbfsize, _p, _up, _bp._base and _bp._size... look at the __sgetc() and __sputc() macros. It's a bit of work. >What should I use instead...? Our local machine has no documentation >on what the fields of _iobuf stand for. Any way you can convince the program it doesn't need this information? Terry Lambert terry@icarus.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. -- ------------------------------------------------------------------------------- "I have an 8 user poetic license" - me