>> Whoops, thought you were wondering this because of the argument order
>> thing. It works pretty much like MemMove does in C, though.
> I think it
>> just takes and does a straight copy over from one memory location to
>> another...it's used similiar to memcpy, I think.
>
>There seems to be so much confusion on this that I thought I
>would do the
>unthinkable
>and look it up in the manual(s) myself:
>
>1. the standard c library function is memcpy destructive.
>2. the PalmOS function MemMove is non-destructive.
>3. there is a function memmove in many c libraries (including
>Visual c++)
>that is also non-destructive.
>4. all three functions take the same arguments (as above,
>which to my mind
>are standard).
Well, I wasn't confused, just had a brief mental lapse at the end of a
VERY long day. (the MemSet argument ordering issue was the first thing
to come to mind) =)
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. It's just a matter of one being destructive
and one not...I believe it's been said on this forum that MemMove should
really be called MemCopy or something like that in order to clear up some
of the confusion, and even though it really isn't Palm's fault that there
IS a memmove function in many libs, it's so commonly used that it may
have been more appropriate to avoid that naming confusion.
-Rus
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
