The standard is to put the function name first and then the body. The analogy should be kept in other definitions similar to functions (if you are autistic enough that you need proof, see alias definitions in shells). So why is C's typedef backwards, first expecting the "body" and then the type? Tsk.
>>1
Because you touch yourself at night and typedef struct { /* my really long struct definition, with 7 factoryfactoryfactories, 23 singletons and 12 pointer to uintmax_t */ } type;
>>5
It would, but typedef type struct { /* my really long struct definition, with 7 factoryfactoryfactories, 23 singletons and 12 pointer to uintmax_t */ }; it's just an unreadable shit.
>>7 42
* /* my really long struct definition, with 7 factoryfactoryfactories, 23 singletons and 12 pointers to uintmax_t and one char pointer */
>>8
Scrolling through the code, }; type is easier to see than typedef type struct union __attribute__ ((pure) (inline) (alwaysinline) (deprecated) (pack 0) (__gnu__faggot__enable__this__)) { /* ...; */ };