This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
Re: Backward compatibility
- From: Brian Jones <cbj at gnu dot org>
- To: Daryl Lee <dlee at altaregos dot com>
- Cc: Mauve Discuss <mauve-discuss at sources dot redhat dot com>
- Date: 27 Dec 2002 19:51:29 -0500
- Subject: Re: Backward compatibility
- References: <20021227171951.GA7889@tigger.localdomain>
Daryl Lee <dlee@altaregos.com> writes:
> I have kind of munged myself from pure test writing to the occasional patch
> to the classpath itself. Now I have a serious issue to raise. Is there
> any intent and/or strategy for backward compatibilty? For example, if the
> 1.1 API says "throw IOException here" and the 1.2 and later APIs say "throw
> FileNotFoundException here", should the 1.1 be ignored in favor of the 1.2?
> Of course, the question applies to far more than exception football. There
> are fundamental behaviors that change, as well.
The current Java 2 (1.4) specification is preferred for Classpath.
Brian
--
Brian Jones <cbj@gnu.org>