Re: regarding memmov( )

[Guy Harris <gharris flashcom net>]

On Wed, Oct 18, 2000 at 12:42:08PM -0700, Kaz Kylheku wrote:
> I would rather spend the time
> finding a design which avoid the memory move entirely, than worry about the
> speed of the memory move.

Or, to put it another way, the *fastest* memory copy is the one you
don't do at all.

(But if you have to do one, "memcpy()" *might* be faster than
"memmove()".  "memcpy()" might not work if the source and destination
overlap, and, on some platforms, an implementation that doesn't try to
make that work might be faster.)