[MPlayer-dev-eng] Use of memcpy with overlapping memory instead of memmove

[armin.gerritsen at philips.com]

>> While I was editing mencoder.c I saw a few memcpy's with potential
>> overlapping source and destination.

> i think that's only of academic interest. or did you see an actual
> memcpy implementation that copies backwards?

I've seen (and created) some of them ... :-)

Point is of course, that it is better to just follow specifications. Just
rely on the fact that most implementations will work anyway, even though it
is not guaranteed, is kind of sloppy IMHO.

Regards,

Armin