(Brent Chapman writes:)
> In all seriousness, though, there is a code maintenance principle that,
> when working on existing programs, you code in the style they were written
> in, even if that's not precisely your own style. Introducing new styles
> only serves to confuse folks who come along later, and don't know the new
> code from the old. This applies to all sorts of things; control constructs
> like those mentioned above, variable naming, variable scoping, use of
> globals, function naming, package organization, indenting conventions,
> commenting conventions, ... Consistency in all these "style issues" makes
> code easier to maintain.
>
For a nice example of a nicely written style guide, check out the one
for Tcl/TK available at ftp://ftp.sunlabs.com/pub/tcl/engManual.tar.Z
You might (or might not) agree with it, but it's certainly clear what
the author wanted to see.
--
----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com -----------
Mad topics slow cleverness
- anagram for "World Class Competiveness" sayeth
http://www.genius2000.com/anagram.html
Follow-Ups:
References:
|
|
