Re: [TUHS] C declarations.

There's no performance "hit" because it doesn't work now. There's really no difference performance or computational complexity wise for char x[4], y[4]; x = y; and struct { char a[4]; } x, y; x = y; About the only thing it would have broken (and would still break today), is the fact that function parameters that are defined to be arrays, really pass pointers. char x[4]; void foo(char a[4]); foo(x); would be costlier than it is now doing the pass by value. Of course you could always fudge if you wanted to pass the pointer by actually doing it that way... char x[4] void foo(char *a); foo(x); -----Original Message----- From: Larry McVoy [mailto:lm@mcvoy.com] Sent: Friday, May 12, 2017 9:24 PM To: Ron Natalie Cc: 'Larry McVoy'; 'David Arnold'; 'The Eunuchs Hysterical Society' Subject: Re: [TUHS] C declarations. On Thu, May 11, 2017 at 06:41:47PM -0400, Ron Natalie wrote: Maybe, just maybe, now that makes sense. But even now that would be a perf hit unless you added some magical copy on write semantics like Tcl has so it can have pass by value semantics but pass by reference performance. Back then, I think the perf hit would have been so bad everyone would be passing arrays as a reference anyway. -- --- Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm