From: Daryl Lee <dlee@altaregos.com>
To: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Backward compatibility
Date: Fri, 27 Dec 2002 09:20:00 -0000 [thread overview]
Message-ID: <20021227171951.GA7889@tigger.localdomain> (raw)
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.
--
Daryl Lee
Open the present--it's a gift.
next reply other threads:[~2002-12-27 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 9:20 Daryl Lee [this message]
2002-12-27 16:51 ` Brian Jones
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=20021227171951.GA7889@tigger.localdomain \
--to=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).