ATOF(3P)
π PROLOG π
okay so first things first, bestie: this manual page is part of the POSIX Programmer's Manual. heads up tho β the Linux implementation of this interface may differ (so go consult the corresponding Linux manual page for the deets on Linux behavior), or the interface may not even be implemented on Linux at all. π
β¨ NAME β¨
atof β convert a string to a double-precision number π
πΈ SYNOPSIS πΈ
#include <stdlib.h>
double atof(const char *str);
π¦ 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, fr β this volume of POSIX.1β2017 defers to the ISO C standard, no cap.
The call atof(str) shall be equivalent to:
strtod(str,(char **)NULL),
except that the handling of errors may differ. π
β οΈ real talk: if the value cannot be represented, the behavior is undefined. like, undefined undefined. don't test it. π
π RETURN VALUE π
The atof() function shall return the converted value if the value can be represented. that's it, that's the whole vibe. β¨
π ERRORS π
No errors are defined. iconically unbothered, honestly. π
The following sections are informative.
π EXAMPLES π
None. (yes literally none, the page said what it said π)
π APPLICATION USAGE π
Okay so here's the tea: the atof() function is subsumed by strtod() but is retained because it is used extensively in existing code. legacy code said "not me being everywhere" and honestly? valid.
But listen β if the number is not known to be in range, strtod() should be used, because atof() is not required to perform any error checking. so if you don't know your input is safe, use the other one. periodt. π₯
π RATIONALE π
None.
π§ FUTURE DIRECTIONS π§
None.
β SEE ALSO β
strtod()- The Base Definitions volume of
POSIX.1β2017,<stdlib.h>
π COPYRIGHT π
okay this is the part where we all sit up straight, because it's the legal bit and it matters:
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 .
and that's the whole page, bestie π«Ά this one came from the IEEE/The Open Group, dated 2017, and it lives in the ATOF(3P) slot in the manual β mwah, take care of her π
π¦ 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