GETS(3P)
π GETS(3P) β the POSIX Programmer's Manual page, bestie edition π
okay so we're in the POSIX Programmer's Manual, and the title is literally GETS(3P). Sit down, grab a boba, because this one is a whole β¨journeyβ¨.
πΈ PROLOG πΈ
so like, this manual page is part of the POSIX Programmer's Manual. but heads up bestie β the Linux implementation of this interface may differ (so if you're on Linux, consult the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface may not even be implemented on Linux at all. π
β¨ NAME β¨
gets β get a string from a stdin stream
π SYNOPSIS π
#include <stdio.h>
char *gets(char *s);
π¦ DESCRIPTION π¦
The functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional β no drama intended fr fr. This volume of POSIX.1β2017 defers to the ISO C standard. π
The gets() function shall read bytes from the standard input stream, stdin, into the array pointed to by s, until a <newline> is read or an end-of-file condition is encountered. Any <newline> shall be discarded, and a null byte shall be placed immediately after the last byte read into the array. so it's giving "read until newline, yeet the newline, null-terminate" energy. π
The gets() function may mark the last data access timestamp of the file associated with stream for update. The last data access timestamp shall be marked for update by the first successful execution of fgetc(), fgets(), fread(), fscanf(), getc(), getchar(), getdelim(), getline(), gets(), or scanf() using stream that returns data not supplied by a prior call to ungetc(). (yes, gets() is in that little list, no she's not special, she's just there π
)
β RETURN VALUE β
Upon successful completion, gets() shall return s. π«Ά
If the end-of-file indicator for the stream is set, or if the stream is at end-of-file, the end-of-file indicator for the stream shall be set and gets() shall return a null pointer.
If a read error occurs, the error indicator for the stream shall be set, gets() shall return a null pointer, and set errno to indicate the error.
π ERRORS π
Refer to fgetc(). that's it, that's the section. go look at fgetc() bestie, it's all over there.
The following sections are informative.
π EXAMPLES π
None. literally none. nothing. crickets. π¦
π APPLICATION USAGE π
okay so THIS is the part where it gets real:
Reading a line that overflows the array pointed to by s results in undefined behavior. The use of fgets() is recommended. π¨
Since the user cannot specify the length of the buffer passed to gets(), use of this function is discouraged. The length of the string read is unlimited. It is possible to overflow this buffer in such a way as to cause applications to fail, or possible system security violations. (not "may cause" β possible system security violations. this function is genuinely a menace π)
Applications should use the fgets() function instead of the obsolescent gets() function. periodt.
π§ RATIONALE π§
The standard developers decided to mark the gets() function as obsolescent even though it is in the ISO C standard due to the possibility of buffer overflow. yeah. that's the whole reason. buffer overflow said "let me ruin this girl's whole career" and the standard developers were like, okay bestie, you're obsolescent now. π
π₯ FUTURE DIRECTIONS π₯
The gets() function may be removed in a future version. so... it's on notice. it's giving "on thin ice" energy. π
π SEE ALSO π
- Section 2.5, Standard I/O Streams
feof()ferror()fgets()
The Base Definitions volume of POSIX.1β2017, <stdio.h>
π COPYRIGHT π
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
that's the whole page bestie, you made it to the end π this little icon was brought to you by IEEE/The Open Group, dated 2017, and it lives under the name GETS(3P). mwah. π«Άβ¨
π¦ where this page comes from
- alpine 3.22: man-pages-posix 2017a-r0 Β· custom
- alpine 3.23: man-pages-posix 2017a-r0 Β· custom
- alpine 3.24: man-pages-posix 2017a-r0 Β· custom
- arch rolling: man-pages 6.19-1
- arch rolling: man-pages 6.20-1 Β· BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
- nixpkgs unstable: man-pages-posix 2017a
- opensuse-leap 16.0: man-pages-posix 2017a-160000.4.1 Β· SUSE-IEEE
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms