Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!rit!cci632!ccicpg!ndjc
From: ndjc@ccicpg.UUCP (Nick Crossley)
Newsgroups: comp.unix.questions
Subject: Re: SysV bcopy?
Summary: bcopy and memcpy/memmove: another difference
Message-ID: <18638@ccicpg.UUCP>
Date: 23 Mar 89 17:30:52 GMT
References: <114@sherpa.UUCP> <216000009@s.cs.uiuc.edu>
Reply-To: ndjc@ccicpg.UUCP (Nick Crossley)
Organization: CCI CPG, Irvine CA
Lines: 13

One other point which no one else seems to have raised yet: the return
value.  memcpy, like strcpy, returns its first argument as a return
value.  No man page for bcopy that I have seen mentions a return value,
so this is not guaranteed.

So, as earlier posters have mentioned, bcopy can usually be replaced by
memcpy or memmove, but the reverse is probably only true if the return
value of memcpy is not used.
-- 

<<< standard disclaimers >>>
Nick Crossley, CCI, 9801 Muirlands, Irvine, CA 92718-2521, USA. (714) 458-7282
uunet!ccicpg!nick  /  nick@ccicpg.UUCP