Do you agree with these guidelines?

I won't argue with you about them. I once (long ago) was expected to work under a set of C programming guidelines that insisted that C header files should be named 'xxxx.C.Header.File'.

It turned out that the job of devising the company's (IBM UK) C programming guidelines had been handed -- by the manager designated to head-up the new project which was their first in C; and whom had never done any C -- to a summer intern (whom had also never done any C). They'd been handed a copy of the companies PL/1 programming guidelines and a copy of "The C programming language" and told to just do it.

It didn't take too long to get some of the more ridiculous ones -- like the file names which the compiler simply couldn't handle -- overturned. Some of the others were directly cribbed from the PL/1 programming standards were harder -- because they were used to them and (presumably) knew their value in that language. It was only when we pointed out that many of them simply had no meaning in the C language that they went out a bought a set of C guidelines from some university.

Not perfect as they were K&R style -- function args named in the parens, but typed between the parens and the opening brace. etc. -- but for the most part, at least familiar.