harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-6648) Character.codePointAt exception differences
Date Tue, 14 Sep 2010 21:44:33 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909465#action_12909465

Robert Muir commented on HARMONY-6648:

I applied the patch with our svn revision 996977 (I fixed the test in 996978), and it cleared
up some test fails, but one remains

this is coming from the following method: 
  public static int codePointAt(char[] seq, int index) { 

It seems this one still throws the generic IIOBE.

By the way, thanks again for uploading the jar files. It makes it trivial to test these things
at the moment.
In the future hopefully I can get myself setup to compile harmony so I can do a better job
with patches/tests here.

> Character.codePointAt exception differences
> -------------------------------------------
>                 Key: HARMONY-6648
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6648
>             Project: Harmony
>          Issue Type: Bug
>          Components: Non-bug differences from RI
>    Affects Versions: 5.0M15
>            Reporter: Robert Muir
>            Assignee: Mark Hindess
>             Fix For: 5.0M16
>         Attachments: luni.jar
> In the Lucene tests, we had a test that looked for expected exceptions from various Character.codePointAt
> The test was written to look for StringIndexOutOfBounds and ArrayIndexOutOfBounds, and
passes because
> people happen to be using an implementation that throws those.
> but the javadocs contract states IndexOutOfBounds, which harmony throws.
> Our test is wrong, but its a small difference.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message