<br><br><div><span class="gmail_quote">On 9/12/07, <b class="gmail_sendername">Steven W Riggins</b> <<a href="mailto:mailinglists@geeksrus.com">mailinglists@geeksrus.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Sep 11, 2007, at 10:59 PM, Jason Johnson wrote:<br><br>> (2)<br>> why did you change it from what you had before?<br>><br><br>Yep, you get alittle bit of this from code control, but not always<br>(people check in massive sets of changes)
<br><br>If I had the skillz/time, I would have a development system that<br>integrated the changes system, and monticello (with many<br>improvements) and the browser.<br><br>1) You can't make a class without a comment. sorry
<br>2) You can't save a method without a comment. sorry The comments<br>would be stored with the changes info<br>3) the source system would implement moderation automatically. </blockquote><div><br>These should be compiler warnings, not errors. Not all methods and classes need comments.
<br><br>Personally I'd rather see a code analysis tool (like lint) that gives you these warnings and summaries about how good your code is.<br><br>Michael.<br></div><br></div><br>