Subject: Re: Performance of various memcpy()'s
To: Bang Jun-Young <firstname.lastname@example.org>
From: Perry E. Metzger <email@example.com>
Date: 10/29/2002 12:10:58
Bang Jun-Young <firstname.lastname@example.org> writes:
> Along with this change, I'd like to get rid of _DIAGNOSTIC stuff as well.
> I don't understand why there's such a pointer wraparound check, since
> the memcpy(3) clearily says "use memmove() for overlap case." It might
> be worth adding "if you're not sure, always use memmove()." comment
> to memcpy(3).
We put stuff like that in place so that people can catch bugs, like
using memcpy if you meant memmove. Believe it or not, people do make
mistakes. It is reasonable to want to have bug-detection mechanisms
available for those who want them.