COMMENTS and PROGRAMMING STYLE
(see also http://courses.cs.cornell.edu/cs100/2000sp/Docs/style.htm)
Thomas Yan

For CS100, we would like you to observe the following principle:

    Principle: Substructures are indented.

This explains indentation for conditionals and loops, and
explains why comments for a group of statements should go above,
with the corresponding statements *indented* *below* the
comment: the corresponding statements are substructures
implementing/fleshing out that statement-comment.

This principle is especially important because good programming
involves breaking larger problems into smaller problems.  The
way the sub-problems fit/nest into the larger problems should be
immediately apparent from the code for maximum clarity.  The
principle above provides that clarity with a simple, unifying
principle consistent with our other conventions for indentation.

However, you should be aware that not everyone uses this
convention.  Sometimes it is not relevant, and sometimes there
are rules/forces against it.  For example, CS312 tends to use a
rather different program language to write rather different
programs, in which other styles might be appropriate.  Another
example is that the instructors use a variety of editors with 
different methods for formatting.

You should apply the principle in your own code for CS100, but
if you would rather not, keep in mind that your project scores
will not suffer unless you make a handful of other errors -- you
can get a perfect score if you make only a few errors.