The penalty is geometrically progressive in .net, VB6 and most environements.
StrngBuilder eliminates that. http://www.4guysfromrolla.com/webtech/092500-1.shtml exlains it well. The person who said that VB6 "extended" string was incorrect. It had the same problem as .net -- some people used some klunky WinAPI calls to beat it but not as elegant as stringbuilder. On 5/12/05, DJ Sampson <[EMAIL PROTECTED]> wrote: > > I have heard that the Stringbuilder class, now, is preferred - instead of > concatenation. > > He told us that, (in DotNet) with concatenation (using +=), that the memory > space, with each addition/concatenation, was totally reallocated, instead of > being extended, like in VB6. > > How much of this is correct and how much can concatenation negatively > affect an application?> > (Does it really matter that much?) Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
