Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watmath.UUCP
Path: utzoo!watmath!water!watbun!kgdykes
From: kgdykes@watbun.UUCP
Newsgroups: net.lang.c
Subject: re Waterloo C compiler
Message-ID: <12309@watmath.UUCP>
Date: Tue, 2-Apr-85 17:19:33 EST
Article-I.D.: watmath.12309
Posted: Tue Apr  2 17:19:33 1985
Date-Received: Wed, 3-Apr-85 01:06:09 EST
Sender: daemon@watmath.UUCP
Organization: U of Waterloo, Ontario
Lines: 31


> From: ATSWAF%UOFT01.BITNET@WISCVM.ARPA (Wendy Fraker)
> Date: 28 Mar 85 19:20:35 GMT
> 
> I need some example programs using the Waterloo C Compiler (don't laugh!)
> our system has it in CMS and I am supposed to become the "expert"
> consultant for it. But it seems that any functions I use for opening or
> reading files don't work properly, even though the same program works
> fine on a VAX using UNIX. Also the backslash N in a printf doesn't work
> ..all printed lines are saved until the program has finished running
> and then they all print at once. Anyone have any possible solutions (be-
> sides using something other than Waterloo C) or examples that I could try
> 
>                            Wendy Fraker (ATSWAF@UOFT01.bitnet)

Just a note from Waterloo here, that is *ONE* of the Waterloo compilers.
 
Re: all printed lines saved until end-of-program, WHO SAYS back-n should
   flush immediately????
   or are you saying even WITH a fflush(), they still wait till program
   termination??
   Also, CMS is essentially batch-oriented, I can easily see batch programs
   holding onto output until it knows its done.
 
From a lackey in the non-IBM land C development at Waterloo....

              - Ken Dykes
                Software Development Group, U. of Waterloo
                Waterloo, Ontario, Canada.  N2L 3G1
                {clyde,utzoo}!watmath!water!watbun!kgdykes