Path: utzoo!attcan!uunet!van-bc!rsoft!mindlink!a218
From: a218@mindlink.UUCP (Charlie Gibbs)
Newsgroups: comp.sys.amiga
Subject: Re: ZC 1.01 Problems
Message-ID: <1970@mindlink.UUCP>
Date: 31 May 90 20:54:48 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 30

In article <20742@snow-white.udel.EDU>
GWO110%URIACC.BITNET@brownvm.brown.edu (F. Michael Theilig) writes:

>     I reciently grabbed ZC off of FF314 and set it up.  Everything got
> set up properly and I created executable properly, but there is one
> annoying side effect.  It seems that ZC won't print out any text until
> a charage return is printed, i.e. when I do a printf with no ending
> n, I don't see the text until one is printed.

     Apparently console output is buffered for speed; the buffer is
dumped when you hit a newline character, or...

>     Is there any way around this?

     Yup.  Just say

        fflush (stdout);        /* or stderr or whatever */

Works fine for me in A68k.

>                                    Also, it seemed that parameters are
> not being taken wrong.  I define argv as *argv[], rather than **argv.
> I haven't looked into that problem thoroughly yet.  Anyone else find
> any problems?

     Jeff Lydiatt mentioned that one when he was working on it.
I found it easier to just switch to **argv.

Charlie_Gibbs@mindlink.UUCP
I'm trying to develop a photographic memory.