From: Andrew Tefft <teffta@engr.dnet.ge.com> Subject: (none) Date: 12 Jul 1993 14:22:05 -0400
"Gerd Klesse" <LH04@IBM3090.RZ.UNI-KARLSRUHE.DE> writes:
|When using 'memcpy' with old TURBO C in ancient days, I was
|used to 'memcpy' to respect overlapping areas.
From "man memcpy" on my sun:
BUGS
[...]
Character movement is performed differently in different implementations.
Thus overlapping moves may yield surprises.
I would guess this applies to Linux's libc as well.
In short, don't assume that functions will always behave consistently
when using them in undocumented fashion (things like this can even change
between library versions).
If you want a memcpy that works the way you're used to, it's simple enough
to write your own -- and then you can be *sure* of its behavior.