Re: Documenting Code (was:Programming language vote - results)

[clin@cs.umd.edu (Charles Lin)]

    One problem with documenting code is that it is often at too fine
a level.   That is, you document individual functions or classes, when
what the user really wants is the overall structure of the code, as
well as how this solution solves the problem.   Sometimes, one practically
wants an overview manual of the code, including the approach to the
solution, the data structures used, and their interactions.

    So, you might have a, say, CAD tool.   You might have objects
that stand for shapes (rectangles, circles), objects that stand
for treating sevearal base objects as a whole.   Objects to keep
track of the state of what is being done (draw, insert, delete,
copy, etc).    Most people would simply comment each of the classes,
but this still gives only a vague idea of how it all fits together.

    I think that producing such a general document might also be
useful for implementors, forcing them to put into words, ideas they
have in their head.   This is esp. important for people who write
code for themselves (or in classes).   By placing idea to paper,
they may clarify muddy thoughts which lead to muddy designs.

--
Charles Lin
clin@cs.umd.edu