Re: Is String.split() broken?

[Jason Abreu <jason.abreu@xxxxxxxxxxxxxxxxxxxx>]

I saw a button at "ThinkGeek.com" that once said:
"Real programmers don't document - if it was hard to write it should be 
hard to understand."
http://www.thinkgeek.com/homeoffice/stickers/9d48/?pfm=Search&t=real%20programmers

Lol.

I'd say when it comes to commenting code, the more the merrier.
I can't say I've ever had anyone complain that I use too many comments.

Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/

On 2/28/2011 12:56 PM, Richard Schoen wrote:
> 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 :-)
>
> Regards,
> Richard Schoen
> RJS Software Systems Inc.
> Where Information Meets Innovation
> Document Management, Workflow, Report Delivery, Forms and Business Intelligence
> Email: richard@xxxxxxxxxxxxxxx
> Web Site: http://www.rjssoftware.com
> Tel: (952) 736-5800
> Fax: (952) 736-5801
> Toll Free: (888) RJSSOFT
>
> ------------------------------
>
> message: 5
> date: Mon, 28 Feb 2011 09:20:51 +0100
> from: Thorbj?rn Ravn Andersen<thunderaxiom@xxxxxxxxxxx>
> subject: RE: Is String.split() broken?
>
> Hi Joe.
>
> 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
> more educated.