Igor Mozolevsky <[EMAIL PROTECTED]> writes:
> 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...
Real memmove doesn't actually move memory either. Why would a function
*move* memory; from an implementation perspective, it would be less
efficient than copying it. I can't conceive of any possible gain to be
had by moving memory; what would the system leave behind in the old
location?
--
Dave Carrigan ([EMAIL PROTECTED]) | Yow! I'm UNEMPLOYED!
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-DNS |
Seattle, WA, USA |
http://www.rudedog.org/ |
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
