[Coco] Unbuffered file pointers in C (Was: INKEY equivalent for C?)

[Bob Devries]

Actually, being a bit pedantic here:

setbuf(stdin, NULL);
setbuf(stdout,NULL);

is more correct, even though, in the OS9 C compiler, no warning is generated 
for the mismatch.
The tamplate is:
#include <stdio.h>
setbuf(fp, buffer)
FILE *fp;
char *buffer;

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "tim lindner" <tlindner at ix.netcom.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, December 27, 2005 2:54 AM
Subject: [Coco] Unbuffered file pointers in C (Was: INKEY equivalent for C?)


> Bob Devries <bdevries at gil.com.au> wrote:
>
>> stdout->_flag |= _UNBUF;
>> stdin->_flag |= _UNBUF;
>
> To set the mode for an I/O stream to be unbuffered, I suggest issuing
> these commands before any I/O is attempted:
>
> setbuf( stdout, 0 );
> setbuf( stdin, 0 );
>
> -- 
> tim lindner
> tlindner at ix.netcom.com                                            Bright
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.7/214 - Release Date: 23/12/2005
>
>