>"Nesse, Rustin" <[EMAIL PROTECTED]> wrote:
>>Part of the problem is that the API has one function, MemMove, that
>>is the equivalent of memcopy, but gets confused with memmove, which is
>>also a very common function.
>
>Errr, it seems correctly named to me. MemMove() can handle
>overlapping copies which makes it equivalent to the standard
>lib function memmove() rather than memcpy().
>--
> -M- [EMAIL PROTECTED]
>
Well, then there's the destructive and non-destructive issue...
but this is all covered (I believe) in the faq, so there's no problem
there. (I think that the only reason there isn't a MemCopy macro is
because it adds a few bytes to the OS size)
-Rus
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
