I agree 100% with what Dalibor just said. Bug reporting systems work OK
sometimes, depending on the situation, but I think the type of bugs
submitted against Kaffe tend to be of a nature where they tend to get
lost in such a system.
I'm going to try hard to personally keep a bug queue (in my ema
> As an aside, I think we need some sort of process for checking in
> patches during a "freeze" like this. Perhaps if two additional people
> sign off on it, and there are no other comments for two days then the
> patch can be checked in?
I did a branch for the release "Release_1_0_7_Branch", so
On Mon, 10 Jun 2002, Dalibor Topic wrote:
> Unless of course you are using reflection to lookup
> the constructor that throws IOException. But
> reflection is not part of JDK 1.1, so no self
> respecting JDK 1.1 app should be using it ;)
It is not? Certainly it's part of the JDK 1.1 API spec
http
--- Patrick Tullmann <[EMAIL PROTECTED]> wrote:
> Jukka wrote:
> I think the way the libraries have been written to
> this point, is to
> follow the most recent available spec as much as
> possible. I think
Yes, as far as I'm concerned ;)
> trying to support different versions of the JDK spec
>
--- Jukka Santala <[EMAIL PROTECTED]> wrote:
> On Sun, 9 Jun 2002, Patrick Tullmann wrote:
> > I fixed this, and some related problems on
> FileOutputStream (its
> > constructors were throwing IOException when they
> may only throw
> > FileNotFoundException, and a 1.4 constructor
> taking (File,
Jukka wrote:
> JDK 1.1 API has the constructors only throwing IOException, though;
> since Kaffe doesn't support full Java2, it is more likely to be ran
> with JDK 1.1 applications.
Actually, I didn't change the exception signature of the constructors.
There was already code that mapped any IOExc
hi Patrick,
--- Patrick Tullmann <[EMAIL PROTECTED]> wrote:
> This strikes me as something that Mauve should have
> tests for (its
> more of a class library problem than a VM-specific
> problem). Can
> anyone who has played with Mauve look and see if
> this is a simple
> addition to that test su
On Sun, 9 Jun 2002, Patrick Tullmann wrote:
> I fixed this, and some related problems on FileOutputStream (its
> constructors were throwing IOException when they may only throw
> FileNotFoundException, and a 1.4 constructor taking (File, boolean)
> was missing). I expanded your test case a bit, t
> I've got the same problem here, and I'll look into a fix (hopefully
> it will be a simple fix).
I fixed this, and some related problems on FileOutputStream (its
constructors were throwing IOException when they may only throw
FileNotFoundException, and a 1.4 constructor taking (File, boolean)
wa
Hi Martin,
Thanks for putting together a nice small example for demonstrating the
problem! I've got the same problem here, and I'll look into a fix
(hopefully it will be a simple fix).
This strikes me as something that Mauve should have tests for (its
more of a class library problem than a VM-s
Hi,
I've a problem with kaffe (version 1.0.7-rc1) on an i686 system with Red
Hat 7.1. I reduced the failure to the following small example.
import java.io.FileInputStream;
import java.io.File;
public class KaffeFile {
public static void main(String[] argv) throws Exception {
File
11 matches
Mail list logo
