1GETCHAR(3P) POSIX Programmer's Manual GETCHAR(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 getchar — get a byte from a stdin stream
13
15 #include <stdio.h>
16
17 int getchar(void);
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 getchar() function shall be equivalent to getc(stdin).
26
28 Refer to fgetc().
29
31 Refer to fgetc().
32
33 The following sections are informative.
34
36 None.
37
39 If the integer value returned by getchar() is stored into a variable of
40 type char and then compared against the integer constant EOF, the com‐
41 parison may never succeed, because sign-extension of a variable of type
42 char on widening to integer is implementation-defined.
43
45 None.
46
48 None.
49
51 Section 2.5, Standard I/O Streams, getc()
52
53 The Base Definitions volume of POSIX.1‐2017, <stdio.h>
54
56 Portions of this text are reprinted and reproduced in electronic form
57 from IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
58 table Operating System Interface (POSIX), The Open Group Base Specifi‐
59 cations Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
60 Electrical and Electronics Engineers, Inc and The Open Group. In the
61 event of any discrepancy between this version and the original IEEE and
62 The Open Group Standard, the original IEEE and The Open Group Standard
63 is the referee document. The original Standard can be obtained online
64 at http://www.opengroup.org/unix/online.html .
65
66 Any typographical or formatting errors that appear in this page are
67 most likely to have been introduced during the conversion of the source
68 files to man page format. To report such errors, see https://www.ker‐
69 nel.org/doc/man-pages/reporting_bugs.html .
70
71
72
73IEEE/The Open Group 2017 GETCHAR(3P)