Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of ricky.clarkson@gmail.com
 designates 64.233.162.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=KRQImAQ/9kzEOyOnzFu2PAQUBw9d1Wy5hAn2CnxEI2F/Bttg4QLnVHxU1kluv8iAVERUIvdD14ux9LTsvaxQU9POfsyxWmXL9i5w0LWunn6nFqkx4QyyD8YPzZASmis+Za3LI7oLkmz8rbLfJaAvJzpgQCQRbo9WH9PblgAR5o8=
Message-ID: <7eeb064605051110383ffce267@mail.gmail.com>
Date: Wed, 11 May 2005 18:38:43 +0100
From: Ricky Clarkson <ricky.clarkson@gmail.com>
Reply-To: Ricky Clarkson <ricky.clarkson@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: cannot leave out deprecated methods, period (was: Re: Java)
In-Reply-To: <20050511171407.GA29127@www.darwinsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4281779C.8090600@anu.edu.au> <4281B6E3.808@earthlink.net>
	 <3847.196.8.104.31.1115801579.squirrel@196.8.104.31>
	 <42823329.90105@earthlink.net> <428235BD.8000409@kaffe.org>
	 <50088f9205051109473faaf7dd@mail.gmail.com>
	 <20050511171407.GA29127@www.darwinsys.com>

Anyway, as I have discovered by overriding deprecated methods from the
API, and experiencing the associated bugs, Sun calls its own
deprecated code, so it's not *that* deprecated. ;)

Some apps rely on deprecated code.  In fact, most Swing apps probably
do, seeing as JDialog.show() is now deprecated (well, Dialog.show(),
which is inherited).

On 11/05/05, Ian Darwin <ian@darwinsys.com> wrote:
> On Wed, May 11, 2005 at 05:47:35PM +0100, FaeLLe wrote:
> > But im still curious do you think TCK checks if Harmony would have
> > implementations of the deprecated methods or can we just spraingly and
> > judging the needs implement a selected few of those.
>=20
> The TCP probably checks for these deprecated methods, but that isn't the =
point.
>=20
> Look, if you're going to all the trouble of reimplementing all of Java yo=
u might
> as well get used to the idea of doing various things that are boring or
> tedious just because you have to. If you don't like that, go play somewhe=
re
> else. Period.
>=20
> Not to mention that it really doesn't save you all that much. The %-age t=
hat is
> deprecated out of the entire J2SE API is fairly small.
>=20
> Think about System.getEnv(). OK, then deprecated but worked, then depreca=
ted
> but threw an exception, and now not deprecated and works again.
>=20
> You do not leave something out just because it's deprecated.  Please do n=
ot
> keep harping on this issue, so people can focus on the (daunting) task at=
 hand.
>