harmony-commits mailing list archives

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

     [ https://issues.apache.org/jira/browse/HARMONY-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Hindess resolved HARMONY-6648.
-----------------------------------

    Fix Version/s: 5.0M16
       Resolution: Fixed

Thanks for the bug report.  Fixed at r997081.  As Tim says in the thread at:

  http://markmail.org/message/7s6533mswansmnm3

we might as well match the RI behaviour since it is an explicit throw.  Please verify (by
closing this JIRA) that this change resolves this issue.


> 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
>
>
> In the Lucene tests, we had a test that looked for expected exceptions from various Character.codePointAt
methods.
> 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.


Mime
View raw message