--On 13 July 2001 20:36 -0500 Ben Combee <[EMAIL PROTECTED]> wrote:
> 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.
I just thought that MemMove did what the SDK reference said, instead of
what real memmove does... Maybe it's time for Palm to 'modify' the
reference to reflect the actual meaning...
IM ;-)
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
