From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1993 invoked by alias); 28 Dec 2002 00:51:47 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 1986 invoked from network); 28 Dec 2002 00:51:47 -0000 Received: from unknown (HELO ncsmtp02.ogw.rr.com) (24.93.67.83) by 209.249.29.67 with SMTP; 28 Dec 2002 00:51:47 -0000 Received: from mail8.nc.rr.com (fe8 [24.93.67.55]) by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id gBS0ooup014710; Fri, 27 Dec 2002 19:50:50 -0500 (EST) Received: from lyta.haphazard.org ([24.74.164.113]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Fri, 27 Dec 2002 19:50:20 -0500 Received: from lyta.haphazard.org (localhost.localdomain [127.0.0.1]) by lyta.haphazard.org (8.12.5/8.12.5) with ESMTP id gBS0pTKH029978; Fri, 27 Dec 2002 19:51:29 -0500 Received: (from cbj@localhost) by lyta.haphazard.org (8.12.5/8.12.5/Submit) id gBS0pTIV029974; Fri, 27 Dec 2002 19:51:29 -0500 X-Authentication-Warning: lyta.haphazard.org: cbj set sender to cbj@gnu.org using -f To: Daryl Lee Cc: Mauve Discuss Subject: Re: Backward compatibility References: <20021227171951.GA7889@tigger.localdomain> From: Brian Jones Date: Fri, 27 Dec 2002 16:51:00 -0000 In-Reply-To: <20021227171951.GA7889@tigger.localdomain> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-q4/txt/msg00090.txt.bz2 Daryl Lee 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