|There's more than one way to do things|
Firstly I only apply this philosophy to Perl, my bad for not stating that explicitly.
IMNTHO anything that has taken 10 years to develop is ripe for rewriting or part of NASA's space project. I think it's daft, having a document dictating how to code, it implies the authors know something (quite often wrong); I prefer a more natural method of buddying developers, that way the learning process is two-way
I've only seen Coding standards work when they were constantly reviewed and altered by the people using them. IME this rarely happens as it involves doing something, it's easier to think write "the coding standard document" and leave it to stifle your developers.
In reply to Re: Re2: To sub or not to sub, that is the question?