> >>I need to know how the function "MemMove" is actually implemented.
> >>Maybe I could get some idea from the source code of MemoryMgr.c.
> >>Could someone quote part of the source code containing "MemMove"?
> >>Or, if it's illegal to quote the source code, could you please
> >>explain how memory content is moved?
> >
> >The PalmOS version of MemMove is a little odd because the order of the
> >arguments is switched around from the usual C version. The prototype
> >is like so:
> >
> >Err MemMove(void *dstP, const void *sP, Int32 numBytes);
>
> 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).
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
