Newsgroups: comp.lang.c
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: memcpy != bcopy (Was Re: bcopy() bzero())
Message-ID: <1990Feb24.233833.14129@utzoo.uucp>
Organization: U of Toronto Zoology
References: <11387@attctc.Dallas.TX.US> <4601@orion.cf.uci.edu> <497@thirdi.UUCP> <22599@mimsy.umd.edu> <1990Feb23.225358.375@sj.ate.slb.com>
Date: Sat, 24 Feb 90 23:38:33 GMT

In article <1990Feb23.225358.375@sj.ate.slb.com> konath@sj.ate.slb.com (Kannan Konath) writes:
>In the VAX-VMS-C manual,  it states that memmove() has exactly the same
>functionality as  memcpy().  Does that mean memmove() does not handle
>overlapped moves or does that mean memcpy() handles overlapped moves.

ANSI C memcpy must not be handed overlapping arguments, whereas ANSI C
memmove is required to handle them correctly.  How this corresponds to
VAX VMS C is another question entirely.
-- 
"The N in NFS stands for Not, |     Henry Spencer at U of Toronto Zoology
or Need, or perhaps Nightmare"| uunet!attcan!utzoo!henry henry@zoo.toronto.edu