Xref: utzoo comp.std.c:546 comp.windows.x:6603
Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!udel!rochester!rutgers!uwvax!astroatc!johnw
From: johnw@astroatc.UUCP (John F. Wardale)
Newsgroups: comp.std.c,comp.windows.x
Subject: bcopy
Message-ID: <1356@astroatc.UUCP>
Date: 9 Dec 88 03:10:39 GMT
References: <9095@smoke.BRL.MIL> <9167@ihlpb.ATT.COM>
Reply-To: johnw@astroatc.UUCP (John F. Wardale)
Followup-To: comp.std.c
Organization: Astronautics Technology Cntr, Madison, WI
Lines: 29

[Sorry it this isn't the "perfect" group for this, but y'all were
 talking about index vs strchr so this can't be too far off.]

What does the following mean?  [What should it do?]

			char a[20];
/* first sample: */
			bcopy (&a[0], &a[1], 19);
/* second sample: */
			bcopy (&a[1], &a[0], 19);

BACKGROUND NOTES:

The vax-BSD 4.3 "man bcopy" doesn't mention this.

 the SUN "man bcopy" says:
"Overlapping strings are handled correctly."

Emacs (a highly ported program) *ASSUMES* (needs/uses) this
overlaping semantic.

This is the libc bcopy, not the kernel version [that's one 
VAX-instructon] or the kernel "ovbcopy"

-- 
					John Wardale
... {seismo | harvard | rutgers | ames} ! {uwvax | cs.wisc.edu} ! astroatc!johnw
                                            or   astroatc!johnw@cs.wisc.edu
To err is human, to really foul up world news requires the net!