"Alberto Gaona" <[EMAIL PROTECTED]> wrote in message
news:56602@palm-dev-forum...
>
> Would it help thinking that the memory moved away and the remaining
area was
> filled with garbage?
>
> (Any one could guess how the garbage looks like ;-) )
>
> But I get the point: every C programmer tends to use memcopy and not
> memmove. Why PalmOS guys decided mount MemMove on the ROM and not
MemCopy?
> Some people on this ng have a story to tell.
MemMove and MemCopy do the same thing, but MemMove is safe for coping
overlapping regions, while MemCopy might do the wrong thing. Since Palm
wanted to minimize ROM space and they already had the overhead of a
trap, it made sense to just implement the safe one.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
