Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates
 74.125.92.150 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=FENa7FBOi2EwFbbhA8QN85MlfA2J45BCAJSC63gFY1FawA4F1vRH4DjurBTjmahaXg
         a36GI2OMWcieW3aimR7Rd1Ah2UmnbrYfwOXosKWYuVUP5PAXI+cOC8Y4GM4w6EvyU4iL
         i6ZKI6u/1VjHW9p/j9RWrGW4IG8JOm30KyQrs=
MIME-Version: 1.0
In-Reply-To: <241871.92934.qm@web112903.mail.gq1.yahoo.com>
References: <241871.92934.qm@web112903.mail.gq1.yahoo.com>
Date: Sun, 7 Feb 2010 22:49:17 -0800
Message-ID: <31cc37361002072249h605e433ek83d3aea597e49c1e@mail.gmail.com>
Subject: Re: [LANG]commons Lang-288
From: Henri Yandell <flamefew@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I disagree on your doubt, but have other doubts. Think of this issue
as a TODO in the code (I think it came from a TODO file a long time
back). I think it's doable with a StrMatcher change - moving it back
to 3.0 because while it shouldn't break the StrTokenizer API, it will
need to break the StrMatcher API.

Hen

On Sun, Feb 7, 2010 at 10:11 PM, Chandra Shekar <reach_chandra@yahoo.com> w=
rote:
> Hi
>
> =A0Can any body clarify my doubt on issue LANG-288; I have added my comme=
nts in it.
>
> Thanks
> Chandrashekar
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org