Re: [TUHS] C declarations.

seemed like a way to define how to look at a wad of memory and they seem to work for me. The problem is they don't work like every other type. Somewhere around the phototypesetter release or V7, they fixed structs to be assignable/passable to functions. They didn't do that for arrays. They retained their half-assed quasipointer status. It would have been easy to bite the bullet back in those days before people codified the inane behavior. For example: struct foo { int a; int b; }; struct foo x; x.a = 1; x.b = 1; struct foo y; y = x; // works fine. struct foo myfunc(struct foo arg) { arg.a = 5; return 5; } y = myfunc(x); // does not modify x Now look at arrays: char x[4] = { 1, 2, 3, 4}; char y[4]; y = x ; // illegal void myfunc(char arg[4]) { arg[0] = 1000; } myfunc(x); // CHANGES X! If had my way, y = x and passing and returning arrays by value would work just like every other C type.