Standards of "style" address only the appearance of code, not it's utility, functionality, correctness, or any other attribute. Enforced consistent style, however, *can* make code more readable to later-in-time maintainers. It can also reveal cases of way-too-deeply-nested if-then-else logic, which I have personally seen reveal non-obvious bugs in highly complex code (missing else clauses). Granted, a good programming editor should be able to catch such errors before they are even compiled, but not everyone has such editors.
Like any other tool, a style enforcer is useful in its place, but it's just one tool. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Sent: Friday, October 21, 2005 5:52 PM To: [email protected] Subject: Re: Code style validation tool >>(I admit, personally, that I'm a tad sceptical about how an automated >>tool can help improve coding standards;... Give a cuisinarte to a bad chef and you still get bad food (faster). _ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
