Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: unknown (asf.osuosl.org: error in processing during lookup of
 archie@dellroad.org)
Message-ID: <436A8418.8090401@dellroad.org>
Date: Thu, 03 Nov 2005 15:41:44 -0600
From: Archie Cobbs <archie@dellroad.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041129
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: Implementation comparisons
References: 
 <OF797D9066.07CFA891-ON802570AE.0074F72C-802570AE.0075E8F9@uk.ibm.com>
In-Reply-To: 
 <OF797D9066.07CFA891-ON802570AE.0074F72C-802570AE.0075E8F9@uk.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

George Harley1 wrote:
> I would like to ask for some opinions on measuring how "correct" a new 
> implementation of a J2SE class is. Consider if someone develops a clean 

Very good question and one that is asked (and sometimes answered)
in various forms all the time on the Classpath mailing list. The
approach there has been pragmatic.. basically the comparision is
of course always versus what the JDK does. If the spec says nothing
but JDK behaves like X, then Classpath typically behaves like X, etc.
If the spec says X and the JDK does Y, then Classpath usually does X.

The harder cases are when the JDK behavior and spec disagree, or the
JDK has a bug but applications rely on that buggy behavior, etc.
These are taken case by case.

-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com