public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Jones <cbj@gnu.org>
To: Daryl Lee <dlee@altaregos.com>
Cc: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Re: API Differences
Date: Fri, 27 Dec 2002 16:50:00 -0000	[thread overview]
Message-ID: <m3k7hvklw6.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <20021227150608.GA6189@tigger.localdomain>

Daryl Lee <dlee@altaregos.com> writes:

> This is VERY helpful.  So helpful, in fact, that the very first two lines
> of output (in the java.io section) raise a general question on testing.
> 
> In the transition from JDK 1.1 to JDK 1.2, Sun redefined the behavior of
> the FileOutputStream(String) constructor.  In 1.1, it threw an IOException;
> in 1.2 (and through 1.4), it throws a FileNotFoundException.
> 
> Since there is only one implementation of the API, and since it is trying
> to be as up to date as possible, a specification change such as this will
> inevitably cause a failure of a 1.1 test, where a 1.2 (or later) test will
> pass.  The general question is "How to handle such changes?"  Or am I
> missing something, like the existence of a classpath archived to the JDK
> 1.1 spec?

This is similar to deprecation, where a method eventually disappears
from the API altogether.  I don't think it's handled in the current
setup but I may be wrong.

My guess is that the 1.1 test for that method must be separated into a
single file and some flag must be invented or convention taken that
lets one specify versions of the JDK the test is okay for and the
choose script modified to deal with it.

Brian
-- 
Brian Jones <cbj@gnu.org>

      reply	other threads:[~2002-12-28  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 12:29 Daryl Lee
2002-12-26 17:45 ` Brian Jones
2002-12-27  4:37   ` Dalibor Topic
2002-12-27  5:28     ` Daryl Lee
2002-12-27  7:06   ` Daryl Lee
2002-12-27 16:50     ` 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=m3k7hvklw6.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).