Bryce McKinlay wrote:
It is not reasonable to expect test case developers ensure that all
tests "run linearly". Exceptions can potentially be thrown at any
time, so to ensure linearity, every check() call would need wrapped
with a try/catch.
If there is a linear sequence of checks in a tes
On 21 Mar 2006 17:36:52 -0700
Tom Tromey <[EMAIL PROTECTED]> wrote:
> > "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>
> > "Stuart" == Stuart Ballard <[EMAIL PROTECTED]> writes:
>
> Stuart> I believe Classpath already has an unchecked NotImplementedException
> Stuart> so that's what I
Andrew John Hughes wrote:
> On 21 Mar 2006 17:36:52 -0700
> Tom Tromey <[EMAIL PROTECTED]> wrote:
>
>
>>>"Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>
>>>"Stuart" == Stuart Ballard <[EMAIL PROTECTED]> writes:
>>
>>Stuart> I believe Classpath already has an unchecked NotImplementedExc
Hmm, and it didn't actually work in Japi for some reason anyway. I'll
investigate.
Stuart.
--
http://sab39.dev.netreach.com/
Hi,
Having a 770 device is not needed. What one needs is a nested X
server that runs the same WM as on the 770 (Matchbox).
Step-by-step instructions:
1. Build classpath
2. Build a JVM
3. Goto http://projects.o-hand.com/matchbox/sources/ and download the
latest version of matchbox-window-ma
> "Stuart" == Stuart Ballard <[EMAIL PROTECTED]> writes:
Stuart> Hmm, and it didn't actually work in Japi for some reason
Stuart> anyway. I'll investigate.
I didn't check it in yet...? Or do you mean that your own test case
for this didn't work?
BTW, I may have found a japi bug. Yesterday
On 22 Mar 2006 09:57:16 -0700, Tom Tromey <[EMAIL PROTECTED]> wrote:
> I didn't check it in yet...? Or do you mean that your own test case
> for this didn't work?
No, I had missed the fact that it wasn't checked in. D'oh!
> BTW, I may have found a japi bug. Yesterday I checked in
> java.text.Bi
Stuart> From that page: "Differences between jdk14 and jdk15 have been
Stuart> ignored. Since these are not counted as good OR bad, they may cause
Stuart> percentages not to add up to 100%"
Thanks. Sorry for the noise.
Tom
> "Wolfgang" == Wolfgang Baer <[EMAIL PROTECTED]> writes:
Wolfgang> It is not really possible to decide what to rip out.
Wolfgang> Distributions already might depend on several stubs for
Wolfgang> compilation of libraries.
Yeah, I agree.
We don't let new stubs in, in general -- that's good.
In going through the stubs, I found java.awt.Image.getScaledInstance().
This method is interesting because it works for most cases, but not
the SCALE_SMOOTH case.
I'm not sure what to do here. I'm inclined to mark it as a stub.
But maybe it isn't that different from any other 'FIXME'... comments?
On 22 Mar 2006 11:27:53 -0700, Tom Tromey <[EMAIL PROTECTED]> wrote:
> I'm not sure what to do here. I'm inclined to mark it as a stub.
> But maybe it isn't that different from any other 'FIXME'... comments?
I'd say as long as it's searchable (ie, FIXME) it's not a terribly big
deal. (Suggestion:
Tom Tromey wrote:
In going through the stubs, I found java.awt.Image.getScaledInstance().
This method is interesting because it works for most cases, but not
the SCALE_SMOOTH case.
I'm not sure what to do here. I'm inclined to mark it as a stub.
But maybe it isn't that different from any other
Bryce> Could JAPI scan for FIXME's as well? These could be flagged as
Bryce> partial/known buggy method implementations.
Nope, japi scans .class files. Hence the (clever :-) hack of a
'throws' clause.
I'm not overly concerned about our ability to find FIXME comments --
grep or eclipse do this ad
--- Comment #2 from csm at gnu dot org 2006-03-22 19:40 ---
Confirmed. This is actually a problem with the KeyGenerator -- classpath's
version can't be used without being initialized.
I am pretty sure it is allowed to use a KeyGenerator without initializing it;
in that case, the class s
We currently make colormap assumptions that cause problems on the Nokia 770.
We need to test this in a nested X setup.
From: Philippe Laporte <[EMAIL PROTECTED]>
To: GNU Classpath
Subject:No need for 770 device to debug the AWT problems
Date: Wed, 22 Mar 2006 16:01:39 +0100 (10:
--- Comment #1 from langel at redhat dot com 2006-03-22 20:08 ---
Done
--
langel at redhat dot com changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #3 from roman at kennke dot org 2006-03-22 20:09 ---
Created an attachment (id=11100)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11100&action=view)
Proposed patch
This patch seems to make the KeyGenerator initialized after beeing created.
However, this only uncovers
Tom Tromey wrote:
Bryce> Could JAPI scan for FIXME's as well? These could be flagged as
Bryce> partial/known buggy method implementations.
Nope, japi scans .class files. Hence the (clever :-) hack of a
'throws' clause.
I'm not overly concerned about our ability to find FIXME comments --
grep o
Bryce> True enough. Presumably, the Classpath coding style or Hacker guide
Bryce> will be updated to mention using the UnimplementedMethodException for
Bryce> stubs.
Yeah, I added a note to the hacking guide.
Probably not enough, but at least there's a mention.
Bryce> I think it should also menti
I should have added that it works fine with the JDK.
Matchbox is kick-ass!
Philippe Laporte wrote:
Hi,
Having a 770 device is not needed. What one needs is a nested X
server that runs the same WM as on the 770 (Matchbox).
Step-by-step instructions:
1. Build classpath
2. Build a JVM
3.
> I should have added that it works fine with the JDK.
> Matchbox is kick-ass!
Well I never thought it could be matchbox's fault.
Matchbox is just the WindowManager - a very little puzzle-part in the
whole picture.
lg Clemens
21 matches
Mail list logo
