SASANO Takayoshi <[email protected]> wrote:
> Does explode.c not replace with memmove()? That's my question.
Imagine a world where people got so paranoid about their memcpy() use, that
they would follow this 2-step process:
1. Replace all memcpy() with memmove(). Absolutely every single one of them.
ALL OF THEM.
2. Then, go re-audit the code, and find the unneccessary ones, where you can
prove you don't need memmove(). Convert those back to memcpy().
a. If the memmove() is not in a performance sensitive place, maybe skip
the validation work and leave it as memmove()...
