1PUTC(3P) POSIX Programmer's Manual PUTC(3P)
2
3
4
6 This manual page is part of the POSIX Programmer's Manual. The Linux
7 implementation of this interface may differ (consult the corresponding
8 Linux manual page for details of Linux behavior), or the interface may
9 not be implemented on Linux.
10
12 putc — put a byte on a stream
13
15 #include <stdio.h>
16
17 int putc(int c, FILE *stream);
18
20 The functionality described on this reference page is aligned with the
21 ISO C standard. Any conflict between the requirements described here
22 and the ISO C standard is unintentional. This volume of POSIX.1‐2017
23 defers to the ISO C standard.
24
25 The putc() function shall be equivalent to fputc(), except that if it
26 is implemented as a macro it may evaluate stream more than once, so the
27 argument should never be an expression with side-effects.
28
30 Refer to fputc().
31
33 Refer to fputc().
34
35 The following sections are informative.
36
38 None.
39
41 Since it may be implemented as a macro, putc() may treat a stream argu‐
42 ment with side-effects incorrectly. In particular, putc(c,*f++) does
43 not necessarily work correctly. Therefore, use of this function is not
44 recommended in such situations; fputc() should be used instead.
45
47 None.
48
50 None.
51
53 Section 2.5, Standard I/O Streams, fputc()
54
55 The Base Definitions volume of POSIX.1‐2017, <stdio.h>
56
58 Portions of this text are reprinted and reproduced in electronic form
59 from IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
60 table Operating System Interface (POSIX), The Open Group Base Specifi‐
61 cations Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
62 Electrical and Electronics Engineers, Inc and The Open Group. In the
63 event of any discrepancy between this version and the original IEEE and
64 The Open Group Standard, the original IEEE and The Open Group Standard
65 is the referee document. The original Standard can be obtained online
66 at http://www.opengroup.org/unix/online.html .
67
68 Any typographical or formatting errors that appear in this page are
69 most likely to have been introduced during the conversion of the source
70 files to man page format. To report such errors, see https://www.ker‐
71 nel.org/doc/man-pages/reporting_bugs.html .
72
73
74
75IEEE/The Open Group 2017 PUTC(3P)