Make clear the bcopy(3) manpage regards when it was marked as LEGACY

as well as when it was removed from POSIX specification.

Reviewed by:		theraven, wblock, bapt, rodrigc
Approved by:		bapt, rodrigc (mentor)
Differential Revision:	D3374
This commit is contained in:
Marcelo Araujo 2015-08-14 01:27:30 +00:00
parent 6790a2583c
commit 6a182dddd9
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=286757

View File

@ -31,7 +31,7 @@
.\" @(#)bcopy.3 8.1 (Berkeley) 6/4/93 .\" @(#)bcopy.3 8.1 (Berkeley) 6/4/93
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd August 13, 2015 .Dd August 14, 2015
.Dt BCOPY 3 .Dt BCOPY 3
.Os .Os
.Sh NAME .Sh NAME
@ -57,18 +57,6 @@ The two strings may overlap.
If If
.Fa len .Fa len
is zero, no bytes are copied. is zero, no bytes are copied.
.Pp
This function is obsolete (marked as LEGACY in
POSIX.1-2001): please use
.Xr memmove 3
in new programs.
Note that
.Fn bcopy
takes its src and dst arguments in the opposite
order from
.Xr memmove 3 .
POSIX.1-2008 removes the specification of
.Fn bcopy .
.Sh SEE ALSO .Sh SEE ALSO
.Xr memccpy 3 , .Xr memccpy 3 ,
.Xr memcpy 3 , .Xr memcpy 3 ,
@ -87,3 +75,25 @@ before it was moved to
for for
.St -p1003.1-2001 .St -p1003.1-2001
compliance. compliance.
.Pp
The
.St -p1003.1-2008
removes the specification of
.Fn bcopy
and it is marked as LEGACY in
.St -p1003.1-2004 .
New programs should use
.Xr memmove 3 .
If the input and output buffer do not overlap, then
.Xr memcpy 3
is more efficient.
Note that
.Fn bcopy
takes
.Ar src
and
.Ar dst
in the opposite order from
.Fn memmove
and
.Fn memcpy .