There absolutely are reasonable alternate ways to represent ordered data that don't involve templates. The way that C does it makes sense in most cases, and if you are looking at something that you cannot understand, you are looking at bad code.
> "Declaration follows use" immediately goes out the window when faced with typedeffed types being used as the base type
Typedefs are an abstraction. If you create a typedef, it is usually because you only want to handle the data as a whole, passing it to helper functions that remove the typedef. Also, declaration of use does not break down with typedefs:
typedef char *(*fn)(int, char *);
fn my_fn;
char *s = (*my_fn)(0, ""); // Proper use
> "Declaration follows use" is the type level equivalent of taking off your socks before taking off your shoes because that's the order in which you put them on.Please give me an example of some C code where this is the case.
std::array isn't a thing in C, so you don't.
huh? where is the extra layer?
std::array<int, 5> array_of_ints = { 1, 2, 3, 4, 5 };
>How do you make a C-array of a given type? Oh boy, "prepend the array specifier before the list of existing array specifiers"?
int c_style_array[5] = {2, 3, 5, 7, 11}; std::array<std::array<int, 3>, 5> array_of_ints;
int c_style_array[5][3];
But the C-style array is more readable, so I am not sure what the complaint really is about.int c_style_array[2][5][3];
There is also no jumping back and forth. C declarations are also recursively constructed. One can complain about the irregularity of pointers syntax.