Path: utzoo!mnetor!uunet!husc6!purdue!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: copying routines, order, and overlap
Message-ID: <10791@mimsy.UUCP>
Date: 25 Mar 88 18:50:39 GMT
References: <7712@apple.Apple.Com> <7485@brl-smoke.ARPA> <10731@mimsy.UUCP> <8803240119.AA21810@hub.toronto.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 19

>In article <10762@mimsy.UUCP> I said that
>>In 4.2BSD, bcopy was allowed to do the copy in any order.

In article <8803240119.AA21810@hub.toronto.edu> thomson@hub.toronto.edu
(Brian Thomson) writes:
>I did a bit of 4.2 porting several (4) years ago, and I distinctly
>remember bcopy() checking for overlap and getting it right.
>I began with VAX "bcopy.s 4.4 9/25/83".  Is this not original 4.2 code?

Possibly not.  There were several `4.2BSD' tapes (just as there
were several `4.1BSD' tapes and several `4.3BSD' tapes, with fixes
quietly inserted).  The SCCS revision files show that rev. 4.2 was
the first one to handle transfers > 65535 bytes; that was done on
83/01/14.  The next change was on 83/09/12: `correct comment on usage';
on 83/09/25 it was changed `to insure that overlapping strings are
properly handled'.  (No substantive changes have been made since then.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris