Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v728)
In-Reply-To: <428236A8.5090805@apache.org>
References: <3498248664443aa9f97730bdc9bc0615@gmail.com>
 <428236A8.5090805@apache.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <43A21938-9561-4F64-A7C8-EAAD81745230@apache.org>
Content-Transfer-Encoding: 7bit
From: "Geir Magnusson Jr." <geirm@apache.org>
Subject: Re: Backward compatibility
Date: Sun, 15 May 2005 12:14:17 -0400
To: harmony-dev@incubator.apache.org


On May 11, 2005, at 12:45 PM, Stefano Mazzocchi wrote:

> Doug Hall wrote:
>
>> Forgive a newbie, but if Harmony passes, would there be an effort  
>> to write the deprecated code? Personally, I would hope not - at  
>> least not initially. But wouldn't it need to include them to pass  
>> compatibility tests (TCK), or do these tests only test the current  
>> API?
>>
>
> Deprecated or non deprecated, we want Harmony to pass the TCK, so  
> whatever the TCK wants us to do, we'll do it.

Yes - to chime in here, we don't just want to squeak by.  We want to  
be just as good as anything else.  We may optimize the deprecated  
APIs later, but we won't avoid doing them - J2SE users expect to have  
those APIs in an implementation that calls itself Java, and so we  
shall :)

geir

-- 
Geir Magnusson Jr                                  +1-203-665-6437
geirm@apache.org