My two cents:
My personal preference is to document as many lines as possible, even if they may be seemingly obvious.
Others may feel that code is self-documenting when often-times it's not because of terse naming or other attempts to write multiple code lines as a single statement.
Maybe it's my fascination with re-stating the obvious, but I think in English whereas some think in code :-)
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Mon, 28 Feb 2011 09:20:51 +0100
from: Thorbj?rn Ravn Andersen<thunderaxiom@xxxxxxxxxxx>
subject: RE: Is String.split() broken?
I am not interested in a code style war, but I am - sincerely, honestly -
interested in hearing why people choose to do it this way (because I
inherited a large codebase in this style). Thanks for a thorough answer.
If others do this kind of commenting, I would appreciate hearing why they
have chosen to do so :) Again, not for the code war, but to become a little
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.