Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: noalias, again
Message-ID: <7577@brl-smoke.ARPA>
Date: 29 Mar 88 13:28:11 GMT
References: <7712@apple.Apple.Com> <7485@brl-smoke.ARPA> <10731@mimsy.UUCP> <7506@brl-smoke.ARPA> <10188@ulysses.homer.nj.att.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <10188@ulysses.homer.nj.att.com> jss@hector (Jerry Schwarz) writes:
>Only by an auxilliary description that describes the semantics
>of strcpy can we be sure what is allowed.  In particular, I assume
>the committee will endorse the rule that any non-overlapping areas
>are ok, but overlapping areas aren't.

You may be right.  I thought one could deduce from "const noalias"
and "noalias" that overlapping was unsafe, but perhaps not.  In any
event, the current draft standard specification for strcpy() does
contain explicit non-overlapping wording.