rogersh%p5c@uk.ac.man.cs (01/21/91)
The version of unixlib I posted recently has a bug in it which
I've just been notified of. Unfortunately it requires a repost to patch
it, which I will do tomorrow. The bug is that fseek() does not correctly
update the position pointer in the stdio FILE struct. Thus ftell() cannot
be relied upon after an fseek(), nor can the return value of fseek().
Apart from this I have had no other bug reports. As an aside this bug was
introduced in the classic way - through correcting another earlier (and
more obscure) problem... :-)
Huw
[ H.J.Rogers (INTERNET: rogersh%p4%cs.man.ac.uk@cunyvm.cuny.edu) ]
[ ,_, (BITNET/EARN: rogersh%p4%cs.man.ac.uk@UKACRL.BITNET) ]
[ :-(_)-o (UUCP: ...!uunet!cunyvm.cuny.edu!cs.man.ac.uk!p4!rogersh) ]
[ _} {_ (JANET: rogersh%p4@uk.ac.man.cs) ]gaspar@urz.unibas.ch (01/22/91)
What's the difference between the UNIX Lib and the Lib that comes with the ANSI C compiler? laci
gtoal@tharr.UUCP (Graham Toal) (01/23/91)
In article <1991Jan21.142158.5230@cns.umist.ac.uk> rogersh%p5c@uk.ac.man.cs writes: > > The version of unixlib I posted recently ... I'm just back from a week's holiday - just a quick note to say thanks for posting the sources! (Unfortunately I haven't yet been able to decode the damned spark file, but I'm sure it will be worthwhile when I do :-) ) Can we expect a flood of reports of successfully posted sources now? (As soon as I've repaired my broken 440 I'm starting on f2c) G -- (* Posted from tharr.uucp - Public Access Unix - +44 (234) 261804 *)