Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Date: Thu, 25 Jun 2009 16:16:26 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Java 1.4.2 or Java6?
In-reply-to: <bf7f828e0906250548t2560e9c0nf2d17ff5abb58c1d@mail.gmail.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <wjo8iqikmm9x.fsf@sun.com>
Organization: Sun Microsystems
References: <bf7f828e0906250445x6c3e1294u565880a1f3b94042@mail.gmail.com>
 <4A4370B3.9020003@sbcglobal.net>
 <bf7f828e0906250548t2560e9c0nf2d17ff5abb58c1d@mail.gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (usg-unix-v)

Tiago Espinha <tiago@espinhas.net> writes:

> It is available in 1.4.2 indeed and that will have to do. The thing is that
> replaceAll uses regex and not regular string matching.
>
> I'm thinking I'll end up dropping the replacing altogether. This was just for
> pruning the output that I am parsing as I go, but I can just not prune it and
> it'll be fine anyway. The trade-off between doing a regex search and having to
> search through some more characters is probably balanced, and regex would
> introduce some more issues in the end.

Note that the String methods that use regex are not part of Foundation
Profile 1.1, so if the test uses those methods it'll have to be disabled
on the Java ME platforms.

-- 
Knut Anders