From: Jim Pick [EMAIL PROTECTED]
Subject: Planning for next release (1.0.7)
Date: Thu, 21 Mar 2002 07:04:32 -0800
Finally, when we decide to do this release, I think we should dedicate it to
the memory of Edouard Parmelan. For those that don't know, he was one of
the most active Kaffe
Jim Pick wrote:
I'll start off the list:
1) Tomcat: http://jakarta.apache.org/tomcat/ - for running servlets
2) Jython: http://www.jython.org/ - see the note saying it doesn't work with
Kaffe at http://www.jython.org/platform.html
3) I'm not going to list too many myself - I want
On Thu, 21 Mar 2002, Jim Pick wrote:
I want to compile a list of what people feel are the most important Java
applications that people will be using kaffe to run.
Important and popular leave bit unclear what is exactly meant, but
I'll add a few programs of interest anyway.
On Thu, Mar 21, 2002 at 07:04:32AM -0800, Jim Pick wrote:
Finally, when we decide to do this release, I think we should dedicate it to
the memory of Edouard Parmelan. For those that don't know, he was one of
the most active Kaffe developers, a member of the core team, and one of the
driving
Date: Friday March 22, 19102 10:03
Author: jim
Update of /cvs/kaffe/kaffe/libraries/javalib/java/net
In directory loco:/tmp/cvs-serv5261/java/net
Modified Files:
DatagramSocket.java
Log Message:
Small fix to DatagramSocket from Timothy Stack (JanOS VM).
I'm so sad (and shocked) to hear this news. I was having lots of email
exchange with Edouard and all of a sudden I couldn't get any response from
him. We were trying to port Kaffe to PowerPC/NetBSD, I was impressed by his
computer skills and his work attitude.
Great idea of dedicating the new
Just a suggestion: could someone strip wc.java down to a testcase that
causes this problem and (assuming its really a compiler problem),
name the testcase BrokenCompilerCheck.java or something? Put it early
in the test run, too.
That will make diagnosing failures much easier in the future.
On Fri, Mar 22, 2002 at 01:17:24PM -0700, Patrick Tullmann wrote:
Just a suggestion: could someone strip wc.java down to a testcase that
causes this problem and (assuming its really a compiler problem),
name the testcase BrokenCompilerCheck.java or something? Put it early
in the test run,
