From: fabio AT joplin DOT colorado DOT edu (Fabio Somenzi)
Subject: Setbuf
3 Nov 1996 20:20:15 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199611040327.UAA01713.cygnus.gnu-win32@joplin.colorado.edu>
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

->On a different subject. Has anyone had problems with setbuf?
->I have a program that calls setbuf(stdin,NULL) and setbuf(stdout,NULL)
->to make a (b)yacc/bison parser work over a pipe. It works well under
->Linux, Solaris, and SunOS, regardless of whether the input comes from
->the terminal or the pipe. Under Win95, all goes well if I don't call
->setbuf, but then I can't use the pipe.

Sorry for the noise. This is explained in Cygnus's online documentation.
In summary, Cygnus's setbuf is non-standard; it seems that file I/O is
not buffered unless explicitly requested to be so with setbuf.

Fabio
--
Fabio Somenzi          | Phone: 303-492-3466
University of Colorado | Fax:   303-492-2758
ECE Dept.              | Email: Fabio AT Colorado DOT EDU
Boulder CO 80309-0425  | WWW:   http://vlsi.colorado.edu/~fabio
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".