I really like seeing work on comments. Have you experimented with doxygen? If you're going to be correcting comments, it might be good to "go the full distance" and make sure that the new comments produce good doxygen docs. Long-term (say, 3-4 months) we could even wrap doxygen into the build system and add that info to the internals reference; this could be a great help to new programmers.
http://codereview.appspot.com/5862052/diff/1/lily/accidental-placement.cc File lily/accidental-placement.cc (right): http://codereview.appspot.com/5862052/diff/1/lily/accidental-placement.cc#newcode116 lily/accidental-placement.cc:116: //TODO: add comment to this class I'm not certain this line adds anything. Also, isn't it a struct, not a class? http://codereview.appspot.com/5862052/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
