Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Abu Yahya <abu_yahya@invalid.com>
Newsgroups: comp.lang.java.programmer
Subject: Re: baseline performance test using java ...
Date: Mon, 04 Jul 2011 00:03:39 +0530
Organization: Aioe.org NNTP Server
Lines: 14
Message-ID: <iuqcm0$tmh$2@speranza.aioe.org>
References: <1309715588.716395@nntp.aceinnovative.com>
NNTP-Posting-Host: nyJO2B725g8xkpRStJY9TQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
X-Notice: Filtered by postfilter v. 0.8.2
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5834

On 7/3/2011 11:23 PM, lbrt chx _ gemale kom wrote:

>>> ~ We have all learned we should avoid String(s) and use
>>> StringBuffer(s) or better yet StringBuilder(s) but there is
> ~
>> Er, no.  Strings are great ...
> ~
>   I (obviously) meant to say String(s) if you need to build them andStringBuilder(s)
 >  if you are working (most of us by now) on some multiprocessing core
> ~

If you need to build them, you'd need a StringBuilder. And if you need 
support for multiple threads AND need to modify them, you'd need a 
StringBuffer.