1MEMMOVE(3P) POSIX Programmer's Manual MEMMOVE(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 memmove — copy bytes in memory with overlapping areas
13
15 #include <string.h>
16
17 void *memmove(void *s1, const void *s2, size_t n);
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 memmove() function shall copy n bytes from the object pointed to by
26 s2 into the object pointed to by s1. Copying takes place as if the n
27 bytes from the object pointed to by s2 are first copied into a tempo‐
28 rary array of n bytes that does not overlap the objects pointed to by
29 s1 and s2, and then the n bytes from the temporary array are copied
30 into the object pointed to by s1.
31
33 The memmove() function shall return s1; no return value is reserved to
34 indicate an error.
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 The Base Definitions volume of POSIX.1‐2017, <string.h>
55
57 Portions of this text are reprinted and reproduced in electronic form
58 from IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
59 table Operating System Interface (POSIX), The Open Group Base Specifi‐
60 cations Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
61 Electrical and Electronics Engineers, Inc and The Open Group. In the
62 event of any discrepancy between this version and the original IEEE and
63 The Open Group Standard, the original IEEE and The Open Group Standard
64 is the referee document. The original Standard can be obtained online
65 at http://www.opengroup.org/unix/online.html .
66
67 Any typographical or formatting errors that appear in this page are
68 most likely to have been introduced during the conversion of the source
69 files to man page format. To report such errors, see https://www.ker‐
70 nel.org/doc/man-pages/reporting_bugs.html .
71
72
73
74IEEE/The Open Group 2017 MEMMOVE(3P)