Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: strcpy
Message-ID: <7521@brl-smoke.ARPA>
Date: 22 Mar 88 19:07:01 GMT
References: <7712@apple.Apple.Com> <7485@brl-smoke.ARPA> <10731@mimsy.UUCP> <10753@mimsy.UUCP> <1304@ut-emx.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <1304@ut-emx.UUCP> wca@ut-emx.UUCP (William C. Anderson) writes:
-In article <10753@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) writes:
--> In article <7506@brl-smoke.ARPA> gwyn@brl-smoke.ARPA (Doug Gwyn) writes:
--> ->This usage was never a good idea, because a valid implementation of
--> ->strcpy() would be to copy right-to-left rather than left-to-right
--> `That turns out not to be the case'---or rather, are you certain?
-Chris is right here, Doug.  For example, the ndbm(3) routines in 4.3BSD
-depend upon bcopy() doing the correct ordering in cases of overlap.

Talk about non-sequiturs!  The subject was strcpy() and the implications
of noalias on its parameters.