Bcopy, bzero and bcmp on a not-Berkeley machine

[Norman Diamond]

In article <1155 at radig.UUCP> peter at 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 at amdahl.uts.amdahl.com> kucharsk at 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 at 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.