Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!megatest!djones
From: djones@megatest.UUCP (Dave Jones)
Newsgroups: comp.lang.c
Subject: Re: Does NEWLINE always flush stdio buffer?
Message-ID: <6074@goofy.megatest.UUCP>
Date: 5 Jul 89 18:17:24 GMT
References: <8045@bsu-cs.bsu.edu)
Organization: Megatest Corporation, San Jose, Ca
Lines: 21

From article <8045@bsu-cs.bsu.edu), by dhesi@bsu-cs.bsu.edu (Rahul Dhesi):
) 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


This came up a year or two ago, and somebody said that it was
going to be "fixed in the next release".  Do you have the latest
and greatest?