Commit 0488e047 authored by araujo's avatar araujo
Browse files

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
parent 6d365c45
......@@ -31,7 +31,7 @@
.\" @(#)bcopy.3 8.1 (Berkeley) 6/4/93
.\" $FreeBSD$
.\"
.Dd August 13, 2015
.Dd August 14, 2015
.Dt BCOPY 3
.Os
.Sh NAME
......@@ -57,18 +57,6 @@ The two strings may overlap.
If
.Fa len
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
.Xr memccpy 3 ,
.Xr memcpy 3 ,
......@@ -87,3 +75,25 @@ before it was moved to
for
.St -p1003.1-2001
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 .
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment