[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#324001: overlapping memcpy()



On Sun, May 21, 2006 at 07:48:39PM -0400, Albert Cahalan wrote:
> On 5/21/06, Thomas Dickey <dickey@radix.net> wrote:
> >On Sun, May 21, 2006 at 05:09:32PM -0400, Albert Cahalan wrote:
> >>
> >> End result: it acts like bzero() when src==dst
> >
> >hmm - someone should fix that broken implementation of memcpy.
> 
> It's damn fast. I like fast libraries, don't you?

I like libraries that produce reasonable results.
 
> The ISO standards for both C99 and POSIX/UNIX state: "If copying
> takes place between objects that overlap, the behavior is undefined."

It may as well dump core then, to encourage people to use a different
implementation.
 
> There wouldn't be a memmove() function if it weren't needed.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Attachment: pgpR5Za5z7AFW.pgp
Description: PGP signature


Reply to: