It seems like Palm could have avoided lots of confusion by just naming this function "MemCopy" instead of "MemMove". After all, everyone is quite familiar with the difference between moving a file and copying one. It also seems like they generally tried to follow the standard C library names as much as possible, e.g. "strcpy" became StrCopy, "memset" became "MemSet", etc. So why did they change "memcpy" to "MemMove"?
Perhaps Palm did follow the C standard. In C memcpy copies a range of bytes without the overhead of checking for overlapping ranges. memmove does the same thing but will work correctly when the source and destination ranges overlap. Presumably Palm felt that the safer of the two methods was the only one needed.
Bob
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
