*BSD News Article 38856


Return to BSD News archive

Xref: sserve comp.unix.bsd:15423 comp.lang.c:86821 comp.unix.sys5.r3:2296
Newsgroups: comp.unix.bsd,comp.lang.c,comp.unix.sys5.r3
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!uunet!deshaw.com!christos
From: christos@deshaw.com (Christos Zoulas)
Subject: Re: how to completely get rid of bcopy, bzero, bcmp?
Message-ID: <D06xy3.Ix8@deshaw.com>
Sender: usenet@deshaw.com
Nntp-Posting-Host: cs4
Organization: D. E. Shaw & Co.
References: <3bksus$fg4@spruce.cic.net> <3bmo74$oan@detroit.freenet.org>
Date: Fri, 2 Dec 1994 16:03:39 GMT
Lines: 19

In article <3bmo74$oan@detroit.freenet.org> brose@detroit.freenet.org (Karl Brose) writes:
>Paul Southworth (pauls@locust.cic.net) wrote:
>>                                 return;  /* too bad */
>>                         bcopy(ptr, def_slcbuf, len);
>>                 }
>
>> What should that bcopy() look like to make this SVR3 system happy?
>
>> Is there a "right" way to implement bcopy() etc on this system so I could
>> generate my own compatibility library and not bother with altering the
>> code every time?
>
>
>#define bcopy(a,b,n)	memcpy((b),(a),(n))

this is not entirely correct. bcopy == memmove since it can handle
overlapping regions; memcpy does not.

christos