1 .\" Copyright (c) 1980, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the American National Standards Committee X3, on Information
6 .\" Processing Systems.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgement:
18 .\" This product includes software developed by the University of
19 .\" California, Berkeley and its contributors.
20 .\" 4. Neither the name of the University nor the names of its contributors
21 .\" may be used to endorse or promote products derived from this software
22 .\" without specific prior written permission.
24 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" @(#)setbuf.3 8.1 (Berkeley) 6/4/93
37 .\" $FreeBSD: src/lib/libc/stdio/setbuf.3,v 1.15 2004/08/24 21:48:21 alfred Exp $
47 .Nd stream buffering operations
54 .Fa "FILE *restrict stream"
55 .Fa "char *restrict buf"
69 .Fa "FILE *restrict stream"
70 .Fa "char *restrict buf"
75 Three types of buffering are available:
76 unbuffered, block buffered, and line buffered.
77 When an output stream is unbuffered, information appears on the
78 destination file or terminal as soon as written;
79 when it is block buffered,
80 many characters are saved up and written as a block;
81 when it is line buffered,
82 characters are saved up until a newline is output
83 or input is read from any stream attached to a terminal device
88 may be used to force the block out early.
92 Normally, all files are block buffered.
95 operation occurs on a file,
97 is called and an optimally-sized buffer is obtained.
98 If a stream refers to a terminal
101 normally does), it is line buffered.
102 The standard error stream
104 is always unbuffered.
109 may be used to alter the buffering behavior of a stream.
112 argument must be one of the following three macros:
113 .Bl -tag -width _IOFBF -offset indent
124 argument may be given as zero
125 to obtain deferred optimal-size buffer allocation as usual.
127 then except for unbuffered files, the
129 argument should point to a buffer at least
132 this buffer will be used instead of the current buffer.
135 is not NULL, it is the caller's responsibility to
137 this buffer after closing the stream.
145 a buffer of the given size will be allocated immediately,
146 and released on close.
147 This is an extension to ANSI C;
148 portable code should use a size of 0 with any
154 function may be used at any time,
155 but may have peculiar side effects
156 (such as discarding input or flushing output)
157 if the stream is ``active''.
158 Portable applications should call it only once on any given stream,
163 The other three calls are, in effect, simply aliases for calls to
165 Except for the lack of a return value, the
167 function is exactly equivalent to the call
169 .Dl "setvbuf(stream, buf, buf ? _IOFBF : _IONBF, BUFSIZ);"
174 is the same, except that the size of the buffer is up to the caller,
175 rather than being determined by the default
180 is exactly equivalent to the call:
182 .Dl "setvbuf(stream, (char *)NULL, _IOLBF, 0);"
186 function returns 0 on success, or
188 if the request cannot be honored
189 (note that the stream is still functional in this case).
193 function returns what the equivalent
216 functions are not portable to versions of
226 always uses a suboptimal buffer size and should be avoided.