You're right Erik,

The rules I've wrote are used in my compagny and were just a compilation of simply rules I could use in different previous compagnies I've worked that make a code readable. They're not changing the way of programming of anyone. For instance this is just the header of a file which is common, or the names of variables or files which are formatted in a given way.

When working with many developpers on the same project, it's important to have the same syntax first to let anyone to read a code wrote by someone else and next for the one who makes the integration of codes from many developpers.

So, this is not something that everybody must use, but ideas on how to write code very readable and with tracability for those who have no idea on how to do.

Never I would ask to the people on 8052.com who want to share their code to follow these rules, but for those who have no specific rules it could be interresting to see how to write code very readable and help them to design their own rules.
Of course it is also very interresting for those who are working in team and especially in some specific applications : I'm working in automotive applications and our customers requires from us to prove the quality and tracability of our code. The rules are also intended for this. Note that some standards like ISO TS16949 are imposing to have a methodolgy allowing to have quality and tracability on the product AND the process...

This is more a question of industrial process than writing readable code...

Stephane