1COPYSIGN(3P) POSIX Programmer's Manual COPYSIGN(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 copysign, copysignf, copysignl — number manipulation function
13
15 #include <math.h>
16
17 double copysign(double x, double y);
18 float copysignf(float x, float y);
19 long double copysignl(long double x, long double y);
20
22 The functionality described on this reference page is aligned with the
23 ISO C standard. Any conflict between the requirements described here
24 and the ISO C standard is unintentional. This volume of POSIX.1‐2017
25 defers to the ISO C standard.
26
27 These functions shall produce a value with the magnitude of x and the
28 sign of y. On implementations that represent a signed zero but do not
29 treat negative zero consistently in arithmetic operations, these func‐
30 tions regard the sign of zero as positive.
31
33 Upon successful completion, these functions shall return a value with
34 the magnitude of x and the sign of y.
35
37 No errors are defined.
38
39 The following sections are informative.
40
42 None.
43
45 None.
46
48 None.
49
51 None.
52
54 signbit()
55
56 The Base Definitions volume of POSIX.1‐2017, <math.h>
57
59 Portions of this text are reprinted and reproduced in electronic form
60 from IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
61 table Operating System Interface (POSIX), The Open Group Base Specifi‐
62 cations Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
63 Electrical and Electronics Engineers, Inc and The Open Group. In the
64 event of any discrepancy between this version and the original IEEE and
65 The Open Group Standard, the original IEEE and The Open Group Standard
66 is the referee document. The original Standard can be obtained online
67 at http://www.opengroup.org/unix/online.html .
68
69 Any typographical or formatting errors that appear in this page are
70 most likely to have been introduced during the conversion of the source
71 files to man page format. To report such errors, see https://www.ker‐
72 nel.org/doc/man-pages/reporting_bugs.html .
73
74
75
76IEEE/The Open Group 2017 COPYSIGN(3P)