Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rice!sun-spots-request
From: etnibsd!sean@cs.utexas.edu (Sean McElroy)
Newsgroups: comp.sys.sun
Subject: Re: scanf on Sun4 & OS 4.0.3
Keywords: SunOS
Message-ID: <2883@brazos.Rice.edu>
Date: 2 Nov 89 14:04:31 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 190, message 3 of 12

In article <2570@brazos.Rice.edu> you write:
>X-Sun-Spots-Digest: Volume 8, Issue 177, message 16 of 16
>
>We recently upgraded out Sun4s to OS 4.0.3.  I recompiled an old program
>which used scanf() for input and found that it no longer understood EOF;
>it just kept running, reusing the last line of the file as the input.  I
>printed out the return code from scanf(), and when it reaches the end of
>file, the return code is 0.  Unfortunately, /usr/5include/stdio.h defines
>EOF as "(-1)".  Reading the lines in via gets() works fine.  Has anyone
>else encountered this problem?  Also, the command "what" no longer gives
>me any SCCS info on the files used to create the executable.  Please send
>email.
>
>Chuck Wilde
>AT&T Bell Labs

I found the same problem.  I contacted Sun and yes that's a bug.  They
sent me copies of the offending objects (regular and profilable versions
for both Sun 3 &4).  They couldn't send me new libraries for some reason
nor can the objects be reinserted into the archive since it is a shared
library.  Anyway if you haven't recieved the new versions by now, I'll be
glad to pack 'em up and send them to you.

  ____,.,_..,__.,_.,__     Sean Philip McElroy
   __'..__._,_.__.__.__    Eaton Corp., SED
   _,___`_.'__.__.__.__    108 Cherry Hill Dr., Beverly, MA 01922
  ___`..'_,___.__.__,_     uunet!etnibsd!sean