Linked by Eugenia Loli on Sun 30th Jul 2006 20:57 UTC
Thread beginning with comment 147837
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-08
As much as reference documentation is concise and complete, many people refuse to read it. These people want the same information rewritten in the form of book, so here you have it. This is the new trend in technical documentation: copy/paste the reference docs, put transitional sentences between the sections, and add synthetic code examples that use the functionality.
On the topic, I just find C#'s string functionality to be a little clunky, especially format strings and the StringBuilder class. I'd much rather use IronPython for text processing tasks in .NET.