Lines Matching refs:output
10 input and output operations on them. As discussed in @ref{I/O
16 * Standard Streams:: Streams to the standard input and output
22 * Simple Output:: Unformatted output by characters and lines.
26 * Block Input/Output:: Input and output operations on blocks of data.
69 input/output library functions. Don't try to create your own objects of
82 the ``standard'' input and output channels that have been established
97 The @dfn{standard output} stream, which is used for normal output from
100 @cindex standard output stream
117 to redirect the standard output to a file, you could do:
121 stdout = fopen ("standard-output-file", "w");
166 output to the stream is appended to the end of the file.
182 but output is always appended to the end of the file.
186 output. When using such a stream, you must call @code{fflush}
257 straightforwardly, but you must be careful if any output streams are
307 you should not use @code{freopen} on an output stream if you have
308 actually done any output using the stream.) Then the file named by
429 the corresponding file to be broken. Any buffered output is written
435 an output stream, because real, everyday errors can be detected at this
437 output, it might get an error because the disk is full. Even if you
475 might not be closed properly. Buffered output might not be flushed and
502 atomically. One example would be if an output line a program wants to
545 generate an output line atomically even in multi-threaded applications
709 larger character sets. What was missing was a possibility to output
851 line-oriented output.
1527 This section describes how to do input and output operations on blocks
1600 @cindex formatted output to a stream
1603 functions) provide a convenient way to perform formatted output. You
1610 most concise way to perform output. These functions are especially
1617 * Table of Output Conversions:: Summary of output conversions and
1625 * Dynamic Output:: Functions that allocate memory for the output.
1641 output stream as-is, while @dfn{conversion specifications} introduced by
1643 formatted and written to the output stream. For example,
1654 produces output like
1688 reasonable free-format output without using any of the modifiers at all.
1689 The modifiers are mostly used to make the output look ``prettier'' in
1700 specification are printed as-is to the output stream. Multibyte
1725 In more detail, output conversion specifications consist of an
1766 field is @emph{not} truncated. Normally, the output is right-justified
1817 @cindex output conversions, for @code{printf}
1825 output, but are different when used with @code{scanf} for input
1888 Note that this conversion specification never produces any output.
1921 @samp{#} flag, the output starts with @samp{0B} instead of @samp{0b}.
1947 @samp{%i}, or @samp{%u} conversions. Using this flag produces output
2080 producing output of the form
2086 producing output of the form
2122 If the value to be printed represents infinity or a NaN, the output is
2127 may result in longer output with information about the payload of the
2129 maximum length of such output.
2195 Here is the output:
2235 the output. In this case more than one output byte can be produced.
2243 terminating null character are written to the output stream. The
2304 The @samp{%n} conversion is unlike any of the other output conversions.
2353 negative value if there was an output error.
2362 negative value if there was an output error.
2368 This function is just like @code{printf}, except that the output is
2375 This function is just like @code{wprintf}, except that the output is
2382 This is like @code{printf}, except that the output is stored in the character
2395 because it can potentially output more characters than can fit in the
2406 This is like @code{wprintf}, except that the output is stored in the
2414 input, excluding the trailing null. If not all output fits into the
2416 a bigger output string. @emph{Note:} this is different from how
2440 been stored in @var{s}. You should try again with a bigger output
2492 The functions in this section do formatted output and place the results
2500 Allocation}) to hold the output, instead of putting the output in a
2543 the same internals as the built-in formatted output functions.
2613 @c output stream, it doesn't use it to release args_value or string in
2958 function that produces the actual output; see @ref{Defining the Output
2970 to register a new output conversion.
2993 The function to register a new output conversion is
3042 @strong{Portability Note:} It is possible to redefine the standard output
3136 This is the character to use for padding the output to the minimum field
3161 which it should write output.
3234 The output produced by this program looks like:
3253 @c the stream, but if this function is called directly, output will be
3353 formatted output facilities. These functions provide a mechanism for
3381 conversions as there is for the corresponding output conversions.
3418 formatted output functions. Partly, this is because it takes some care
3545 determines whether the output is stored as a wide character string or a
3561 determines whether the output is stored as a wide character string or a
3578 byte of output and therefore the provided buffer must be large enough for up
3589 by the @samp{%p} output conversion for @code{printf}. @xref{Other Input
3699 @code{float *}. (This is different from the corresponding output
3770 at most @var{n} wide characters get stored in the output string.
3898 the same syntax used by the @samp{%p} output conversion for
4006 the same internals as the built-in formatted output functions.
4007 These functions are analogous to the @code{vprintf} series of output
4144 descriptors. For example, all of the functions that perform output to a
4205 binary data, and the input and output facilities of @w{ISO C} provide for
4344 @code{fseek} either flushes any buffered output before setting the file
4590 as soon as they are output by the application program. Similarly,
4594 If you are writing programs that do interactive input and output using
4596 user interface to your program. Otherwise, you might find that output
4607 low-level input and output functions that operate on file descriptors
4612 * Flushing Buffers:: How to ensure that output buffers are flushed.
4645 The use of line buffering for interactive devices implies that output
4649 should flush buffered output explicitly with @code{fflush}, as described
4656 @dfn{Flushing} output on a buffered stream means transmitting all
4658 buffered output on a stream is flushed automatically:
4662 When you try to do output and the output buffer is full.
4679 If you want to flush the buffered output at another time, call
4686 This function causes any buffered output on @var{stream} to be delivered
4688 @code{fflush} causes buffered output on @emph{all} open output streams
4705 required and the program wants to be sure that all output is visible on
4721 been known to be so thoroughly fixated on line-oriented input and output
4726 In some situations it might be useful to not flush the output pending
4728 and the output is not needed anymore this is valid reasoning. In this
4737 input in the buffer is lost. If the stream is in output mode the
4738 buffered output is not written to the device (or whatever other
4762 @code{_IONBF} (for unbuffered input/output).
4894 function returns the number of bytes currently in the output buffer.
4907 One such type of stream takes input from or writes output to a string.
4912 More generally, you can define streams that do input/output to arbitrary
4924 input data source and/or output data sink.
4981 This program produces the following output:
5003 remain valid only as long as no further output on the stream takes
5004 place. If you do more output, you must flush the stream again to store
5022 This program produces the following output:
5035 arbitrary data source or writes output to an arbitrary data sink
5201 input-room and output-room functions. These functions must
5316 There is another way certain fields can be omitted from the output to
5344 If no parameter is ignored the output looks like this:
5368 output actually happening on standard error (@emph{not} the console
5369 output). Each of the five fields can explicitly be enabled. To do
5476 @code{SEV_LEVEL} function produces the following output:
5485 three calls to @code{fmtmsg} produced output. The first call does not
5489 produced no output since the class with the numeric value @code{6} is
5492 the second call to @code{fmtmsg} produces the above output.
5504 Now the third call to @code{fmtmsg} produced some output and we see how
5508 Now we can reduce the output by specifying which fields we are
5511 following output:
5521 I.e., the output produced by the @var{text} and the @var{tag} parameters
5523 after the @code{NOTE} and @code{NOTE2} strings in the output. This is
5524 not necessary since there is no more output on this line because the text