From: Brian Jones <cbj@gnu.org>
To: Daryl Lee <dlee@altaregos.com>
Cc: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Re: Backward compatibility
Date: Fri, 27 Dec 2002 16:51:00 -0000 [thread overview]
Message-ID: <m3fzsjklta.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <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>
prev parent reply other threads:[~2002-12-28 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 9:20 Daryl Lee
2002-12-27 16:51 ` Brian Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fzsjklta.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=dlee@altaregos.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).