🚀 go-pugleaf

In article <1895@skye.ed.ac.uk> jeff@aiai.UUCP (Jeff Dalton) writes:
>In article <14203@lambda.UUCP> jlg@lambda.UUCP (Jim Giles) writes:
>>You just made it.  In C there is _NO_DIFFERENCE_ between a pointer and
>>an array. 
>
>Can't assign to something declared as an array.

Not again?!  In C, there is no difference twixt and 'tween the two, provided
it gets passed as an argument to a function.  With, however:

	int a[100];
	int b[100];
	void foo(int x, int y, int z) {
		/* do whatever with a and b */
	}

the compiler does *not* have to worry about aliasing.  If a function is
called, it *does* have to worry about a and b changing (unless they are
static, and no pointers were passed out, which a compiler *can* be aware of
fairly easily).  Voila:  no aliasing problems.

With pointers, however, it is a bit different.

-- 
Sean Eric Fagan  | "Time has little to do with infinity and jelly donuts."
seanf@sco.COM    |    -- Thomas Magnum (Tom Selleck), _Magnum, P.I._
(408) 458-1422   | Any opinions expressed are my own, not my employers'.