X-Received: by 10.224.72.199 with SMTP id n7mr1757125qaj.5.1361903605628; Tue, 26 Feb 2013 10:33:25 -0800 (PST)
X-Received: by 10.49.106.131 with SMTP id gu3mr894232qeb.36.1361903605605; Tue, 26 Feb 2013 10:33:25 -0800 (PST)
Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!t2no5216962qal.0!news-out.google.com!t2ni1780qaj.0!nntp.google.com!dd2no3308127qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.java.programmer
Date: Tue, 26 Feb 2013 10:33:25 -0800 (PST)
In-Reply-To: <kginuf$5s2$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.28.149.29; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T
NNTP-Posting-Host: 69.28.149.29
References: <qa8pi8tgm6kpbcn19l69rfvbclio6spivt@4ax.com> <kginuf$5s2$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <bc630117-b6e4-4e0f-8b37-2466eafe54fc@googlegroups.com>
Subject: Re: simple StringBuilder proposal
From: Lew <lewbloch@gmail.com>
Injection-Date: Tue, 26 Feb 2013 18:33:25 +0000
Content-Type: text/plain; charset=ISO-8859-1
X-Received-Bytes: 2139
Xref: csiph.com comp.lang.java.programmer:22547

markspace wrote:
>  Roedy Green wrote:
>> With FastCat, I can write: 
>> 
>>   sb.append( "<input name=\"cx\" type=\"hidden\" value=\"", cseAccount,
>> ":", cseCode, "\">\n" );
> 
>> It is just shorthand for
> 
>> sb.append( "<input name=\"cx\" type=\"hidden\" value=\"",)
>> sb.append(cseAccount);
>> sb.append(":");
>> sb.append(cseCode);
>> sb.append( "\">\n" );
> 
>> I propose StringBuilder learn the same trick.

Java already has a shorthand for that:

  String s = "<input name=\"cx\" type=\"hidden\" value=\""
              + cseAccount + ":" + cseCode +  "\">\n";

> I think I see what you are saying.  Java 8 is "in the chute" *right 
> now*, so it might be timely to send in an enhancement request.  I don't 

Adding a feature that already exists is not an enhancement.

> think they're feature complete yet.

It is not the job of the API to provide every conceivable cover method for 
every conceivable combination of use cases. Good thing, too, or we programmers 
would have no jobs.

-- 
Lew