Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.lang.c
Subject: Re: Does NEWLINE always flush stdio buffer?
Keywords: stdio printf I/O
Message-ID: <8045@bsu-cs.bsu.edu>
Date: 4 Jul 89 04:42:07 GMT
References: <11012@ihlpl.ATT.COM> <18351@mimsy.UUCP>
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 15

In article <18351@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
   I feel the best approach is for applications to set all output files
   to `fully buffered', and then to use fflush whenever the output is
   supposed to appear.  This never produces surprises...

...except under VAX/VMS which, when you run a batch job, interprets

     fflush(stdout);
	  
to mean:

     printf("\n");
-- 
Rahul Dhesi <dhesi@bsu-cs.bsu.edu>
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi