This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: FYI: java.io.Writer fixlet from GNU Classpath

From: Tom Tromey <tromey at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: Mark Wielaard <mark at klomp dot org>, java-patches at gcc dot gnu dot org
Date: 17 May 2004 12:50:07 -0600
Subject: Re: FYI: java.io.Writer fixlet from GNU Classpath
References: <1084732645.29428.21.camel@elsschot.wildebeest.org><16552.34752.564678.551514@cuddles.cambridge.redhat.com>
Reply-to: tromey at redhat dot com

Andrew> I'm wondering what the justification for the Mauve test is.

How does the JDK do on this test?

Andrew> The old Java spec (2nd ed, paper copy) says that "lock" must be
Andrew> non-null, but the current online spec says just "lock - Object to
Andrew> synchronize on."

Yeah, but it doesn't make sense for this to be null.
This is a minor point, but I suppose we might as well be compatible
and throw the exception early if the JDK does.

Tom

Follow-Ups:
- Re: FYI: java.io.Writer fixlet from GNU Classpath
  - From: Andrew Haley

References:
- FYI: java.io.Writer fixlet from GNU Classpath
  - From: Mark Wielaard
- FYI: java.io.Writer fixlet from GNU Classpath
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]