> So summing up, I think a coding standard should consist of
> a) an automated formatting tool (JCF or DelFor using a
> DUnit-specific configuration set), plus
> b) a *concise* set of *justified* rules, with a clear
> distinction between requirements and recommendations;
> c) After automated (re)formatting of code, manual compliance
> verification should embody a checklist
> of no more than 10-15 core requirements.
I agree with all that, but the reason we adopted a coding standard for
this project was to have uniformity in the source code. The original
group of developers had no objections on adopting just any standard,
thow preference was towards something compatible with how Borland codes
the Delphi libraries.
If you know of another coding standard that meets that criteria and
yours, bring it on.