Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: SysV bcopy?
Message-ID: <1214@auspex.UUCP>
Date: 26 Mar 89 02:31:24 GMT
References: <114@sherpa.UUCP> <216000009@s.cs.uiuc.edu> <18638@ccicpg.UUCP>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 8

>One other point which no one else seems to have raised yet: the return
>value.

I think the reason nobody raised this is that the return value of
"memcpy" is, in most cases, singularly useless; if I'd wanted the value
of the first argument to "memcpy", I would have used it directly.  I
cannot remember *ever* having used either the return value of "memcpy"
*or* the return value of "strcpy" in any code I've written.