@d_pechkin @erabo and I emphasize that I write in C all these years. so the code clarity and code style is important and should not allow things like 'int* x'. because they're principally wrong and may lead to errors if the code is changed later. and it means that people don't understand the C typing and type assotiation rules. and then they cannot understand a little more complicated things like 'int *(*f)(int *x);' and so on. because they have a chaos in their head and mistake common declarations and evaluations. and note that (*f) means a pointer to function, because pointer is attached to the defined object, not to the type it dereferences.
the example of proper code style is the Kernel coding style: clear and fine. I think that coding style is important.