Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!decvax!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Clarification needed on Pointers/Arrays
Message-ID: <11914@haddock.ima.isc.com>
Date: 1 Mar 89 18:55:13 GMT
References: <1436@etive.ed.ac.uk> <889@acf3.NYU.EDU> <11840@haddock.ima.isc.com> <890@acf3.NYU.EDU>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 14

In article <890@acf3.NYU.EDU> sabbagh@acf3.UUCP () writes:
>	int a[10],b[10];
>	...
>	a = b;
>
>is easy enough to interpret as array copy, but it be a "high-level" construct
>that is not found in other semantic areas of C.

Not so.  C has had struct copy for the last decade; I understand that array
copy was not added at the same time only because they couldn't find a clean
way to fit it into the existing language.  The invention of prototypes did
provide a (relatively) clean path, but unfortunately X3J11 didn't take it.

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint