From owner-freebsd-arch Sun Mar 16 12:36:57 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 622FD37B401 for ; Sun, 16 Mar 2003 12:36:56 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 309CE43FAF for ; Sun, 16 Mar 2003 12:36:55 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h2GKaqDs009358 for ; Sun, 16 Mar 2003 21:36:53 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: arch@freebsd.org Subject: memcpy() with specified direction of copying ? From: Poul-Henning Kamp Date: Sun, 16 Mar 2003 21:36:52 +0100 Message-ID: <9357.1047847012@critter.freebsd.dk> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there any standard which has provided an api for mandating the direction of copying from a memcpy() like function ? As I read our man-page, there is no way to know of memcpy() copies from the start and forward or from the end and backward through the two areas. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message