Xref: utzoo comp.lang.c:22333 comp.unix.questions:16613 comp.unix.wizards:18370 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!kddlab!titcca!sragwa!wsgw!socslgw!diamond From: diamond@csl.sony.co.jp (Norman Diamond) Newsgroups: comp.lang.c,comp.unix.questions,comp.unix.wizards Subject: Re: Bcopy, bzero and bcmp on a not-Berkeley machine Keywords: bcopy bzero bcmp berkely system_v Message-ID: <10884@riks.csl.sony.co.jp> Date: 27 Sep 89 11:47:24 GMT References: <1155@radig.UUCP> <13p902Mz5aZY01@amdahl.uts.amdahl.com> Reply-To: diamond@riks. (Norman Diamond) Followup-To: comp.lang.c Organization: Sony Computer Science Laboratory Inc., Tokyo, Japan Lines: 27 In article <1155@radig.UUCP> peter@radig.UUCP (Peter Radig) writes: > >Is is possible to replace calls to `bcopy', `bzero' and `bcmp' by > >the following macros: > > #define bcopy(fr,to,cnt) memcpy(to,fr,cnt) In article <13p902Mz5aZY01@amdahl.uts.amdahl.com> kucharsk@amdahl.uts.amdahl.com (William Kucharski) writes: > The big difference between bcopy and memcpy is that bcopy is defined to > handle copies of overlapping ranges of memory correctly while memcpy's > behavior in the same situtation is implementation and/or architecture > dependent. Where is it guaranteed that bcopy handles overlapping ranges correctly? It's not in the BSD 4.3 man page. >| Saying: "It's a window system named 'X,' NOT a system named 'X Windows'" | Ah, but what do you CALL the name? -- H. Dumpty (per L. Carroll). -- -- Norman Diamond, Sony Corporation (diamond@ws.sony.junet) The above opinions are inherited by your machine's init process (pid 1), after being disowned and orphaned. However, if you see this at Waterloo or Anterior, then their administrators must have approved of these opinions.