harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-696) Harmony regex does not support Character.isXXX character classes
Date Thu, 29 Jun 2006 17:42:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-696?page=all ]

Nikolay Kuznetsov updated HARMONY-696:

    Attachment: charclasses.patch

The attached patch contains fixes for this issue and unit test update for added functionality.

Current implmentation of Harmony java.util.regex package(as well as this patch) does not support
supplementary characters. For more details and comments on supplementary character support
please refer to HARMONY-688.

> Harmony regex does not support Character.isXXX character classes
> ----------------------------------------------------------------
>          Key: HARMONY-696
>          URL: http://issues.apache.org/jira/browse/HARMONY-696
>      Project: Harmony
>         Type: Bug

>   Components: Classlib
>  Environment: All
>     Reporter: Nikolay Kuznetsov
>  Attachments: charclasses.patch, charclasses_tests.patch
> According to JavaDoc specification java.util.regex.Patter should provide character classes
corresponding to all Character.isXXX methods except deprecated:
> "Categories that behave like the java.lang.Character boolean ismethodname methods (except
for the deprecated ones) are available through the same \p{prop} syntax where the specified
property has the name javamethodname."
> Harmony implementation supports only for, which named directly in the spec:
> java.lang.Character classes (simple java character type) 
> \p{javaLowerCase} Equivalent to java.lang.Character.isLowerCase() 
> \p{javaUpperCase} Equivalent to java.lang.Character.isUpperCase() 
> \p{javaWhitespace} Equivalent to java.lang.Character.isWhitespace() 
> \p{javaMirrored} Equivalent to java.lang.Character.isMirrored() 
> The others should be also implemented.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message