Stefan Roas <sroas@roath.org> (2013-11-23): > On Sat Nov 23, 2013 at 10:18:43, Robert Baron wrote: > > Second question: > > > > Doesn't memcpy allow for overlapping memory, but strcpy does not? Isn't > > this why memcpy is preferred over strcpy? > > Nope. There's memmove for overlapping areas. Indeed, easy enough to check anyway, "opengroup memcpy" gives you: http://pubs.opengroup.org/onlinepubs/007904975/functions/memcpy.html Quoting it: The memcpy() function shall copy n bytes from the object pointed to by s2 into the object pointed to by s1. If copying takes place between objects that overlap, the behavior is undefined. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature