I had way too much caffeine and way too much free time yesterday so that wasn't
helping any. Your fix works fine, of course.
Thanks, george
-Original Message-
From: Andy Clark [mailto:[EMAIL PROTECTED]
Sent: Friday, February 04, 2000 3:47 PM
To: [EMAIL PROTECTED]
Subject: Re
"George T. Joseph" wrote:
> Jeez, you're making me sorry I even spoke up. I set the test
> code to end at 128 because that is what YOU guys do in
> DeferredDocumentImpl.
I'm sorry if I gave you that impression. I'm extremely busy
at the moment and just quickly checked to make sure that the
bi
ust before "int value = values[middle];" (where the exception
is thrown) and run it through DOMCount.
-Original Message-
From: Andy Clark [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2000 7:23 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBoundsE
"George T. Joseph" wrote:
> int[] n = new int[128];
> for(int i=0;i int rc = DeferredDocumentImpl.binarySearch(n, 0, 128,
> Integer.parseInt(argv[0]));
> System.out.println("Index: "+rc);
The start and end points passed into the binarySearch method
are INCLUSIVE. Therefore, you are causin
argv)
{
int[] n = new int[128];
for(int i=0;imailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2000 2:48 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBoundsException: 128
"George T. Joseph" wrote:
>
> Don't be so quick to blame HotSpot here!! This f
"George T. Joseph" wrote:
>
> Don't be so quick to blame HotSpot here!! This fails with Karen's files on
> Sun
> win32 1.2.2 both classic and HotSpot and also on IBM Win32 1.1.8.
We've had a lot of problem with HotSpot causing people to report
false bugs. HotSpot *does* have problems because mo
where start=end=middle=128 and that's not a valid index in a array of
128 elements.
Either call binarySearch with fIdCount-1 or change start<=end to startmailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2000 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBou
You should dump Hotspot. It has problems running correct Java class
files, that
other VM's (Sun Classic JVM, IBM JVM, etc.) have no trouble running.
At least, that is our experience with Hotspot.
Mike
Karen Schuchardt wrote:
>
> This is in reference to a previous mail under the same subject.
Let me take a wild guess... You are using Java 1.2.2 with HotSpot.
Am I right? A lot of people are reporting erroneous array index
expections because HotSpot is buggy. If you are using HotSpot,
please turn it off and try again. If your problem persists, we'll
take a look at it.
P.S. Always include
