https://www.na-mic.org/w/index.php?action=history&feed=atom&title=StyleCheckSummary 2026-04-07T04:00:03Z Revision history for this page on the wiki MediaWiki 1.33.0 https://www.na-mic.org/w/index.php?title=StyleCheckSummary&diff=4190&oldid=prev 2006-12-18T13:37:43Z

<p>Update from Wiki</p> <p><b>New page</b></p><div>== Description ==<br /> <br /> Discussing software coding style is akin to discussing religion. Although everybody thinks their style is the correct one, in actuality there are higher principles that guide the various philosophies, and in the end all philosophies try to do the right thing. These principles include clarity, consistency, self-documentation, compactness, maintainability, and error reduction to name just a few. Another important goal is to reduce the learning curve by making the code look like it was written by a single developer. This assists in the visual processing of large amounts of code.<br /> <br /> Often associated with programming style are programming methodologies, for example, insuring that every class contain a PrintSelf() method, or insuring that no public data members are defined. In NAMIC, when we refer to style we also implicity include all the methodologies that go along with a system.<br /> <br /> == Role In NAMIC ==<br /> <br /> Programming styles are enforced across software systems. For example, [[VTKSummary|VTK]], [[ITKSummary|ITK]], and [[CmakeSummary|CMake]] all enforce a particular style. Typically style guides are associated with each project. Software created for NAMIC will follow local project style guidelines, with any new software projects adopting styles consistent with other systems in the NAMIC software inventory.</div>

Andy