This is the mail archive of the
mailing list for the Mauve project.
Re: failure notice
- From: Dalibor Topic <robilad at yahoo dot com>
- To: tromey at redhat dot com
- Cc: mauve-discuss at sources dot redhat dot com
- Date: Thu, 13 Jun 2002 14:39:28 -0700 (PDT)
- Subject: Re: failure notice
--- Tom Tromey <email@example.com> wrote:
> >>>>> "Dalibor" == Dalibor Topic <firstname.lastname@example.org>
> Dalibor> The constructor of the test subsclass for
> Dalibor> java.io.PrintStream is broken: it calls
> Dalibor> constructor of PrintStream with an
> OutputStream of
> Dalibor> null.
> Thanks. I've changed it to use System.out.
> What do you think of that?
Yes, that's better. It works for current kaffe, gij
3.1 and jdk 1.4.0. It's only needed temporarily
anyway, and gets replaced in the test by the
> Does the PrintStream constructor require an
> exception if the argument
> is null? Or is this just a QoI thing?
the spec is silent on it (up to JDK 1.4.0 at least).
The Java Class Libraries Book 2nd Ed Vol 1 by Chen et
al says the constructor requires a non-null output
> Do you want Mauve write access? That might be best
> if you plan to
> hack on it more.
I'd like to migrate some tests from kaffe over to
mauve. So write access would be nice, but not really
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup