The second arg in the prototypes for memmove/memcpy/strcpy are similar: For example:
void *memmove(void *dest, const void *src, size_t n); //const void*
char *strcpy(char *dest, const char *src); //const char*
But apparently, if dest and src overlap, then src's content will be altered, violating the const void/char *?
const void*
means that the referand will not be modified through that pointer.
If there are other, non-const pointers to the same object (also known as "aliasing"), then of course it can still be modified through those. In the scenario you describe, that other pointer is dest
.
By the way, in the case of strcpy
, behavior is undefined if the regions overlap, and in C99 the signature is char *strcpy(char * restrict s1, const char * restrict s2);
. But for memmove, aliasing is OK. By giving it overlapping regions you've given it "permission" to modify the dest
region, and it will do that.
The argument is marked const void *
to indicate memmove
will never modify the memory pointed to by src
using that pointer. If overlap occurs the memory is modified using the dest
pointer, not the src
pointer, so the guarantee is not violated.
It means memmove
guarantees it won't directly modify the memory pointed by src
.
Of course if the two blocks overlap memmove
will change the so-called "const" memory. const
is ca contract attached to a name. There's no way to make the actual memory read-only.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With