Date: Fri, 29 May 1998 17:29:18 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Terry Lambert <tlambert@primenet.com> Cc: mike@smith.net.au (Mike Smith), joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Message-ID: <16517.896488158@time.cdrom.com> In-Reply-To: Your message of "Fri, 29 May 1998 23:30:55 -0000." <199805292330.QAA23999@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> While we are on the subject of portability problems, doesn't anyone
> else find it annoying that memcpy() is not guaranteed to work on
> overlapping memory ranges, yet we are migrating bcopy() to memcpy()
> as time goes on? Grrrr...
Who's "we", white man? :-)
...
STANDARDS
The memcpy() function conforms to ISO 9899: 1990 (``ISO C'').
BUGS
In this implementation memcpy() is implemented using bcopy(3), and
therefore the strings may overlap. On other systems, copying overlapping
strings may produce surprises. A simpler solution is to not use
memcpy().
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16517.896488158>