From owner-freebsd-current Fri May 29 17:29:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09903 for freebsd-current-outgoing; Fri, 29 May 1998 17:29:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09895 for ; Fri, 29 May 1998 17:29:46 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA16521; Fri, 29 May 1998 17:29:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert 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 In-reply-to: Your message of "Fri, 29 May 1998 23:30:55 -0000." <199805292330.QAA23999@usr05.primenet.com> Date: Fri, 29 May 1998 17:29:18 -0700 Message-ID: <16517.896488158@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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