[ 
https://issues.apache.org/jira/browse/LANG-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329129#comment-14329129
 ] 

Arno Noordover edited comment on LANG-1069 at 2/20/15 4:31 PM:
---------------------------------------------------------------

I tried to show with this example that parsing is executed from left to right. 
So the set containing a ^ is negated. The second ^ could also negate the set 
containing a-d and then interpreting the first ^ in some undefined way.


was (Author: anoordover):
I tried to show with this example that parsing is execute from left to right. 
So the set containing a ^ is negated. The second ^ could also negate the set 
containing a-d and then interpreting the first ^ in some undefined way.

> CharSet.getInstance documentation does not clearly explain how to include 
> negation character in set
> ---------------------------------------------------------------------------------------------------
>
>                 Key: LANG-1069
>                 URL: https://issues.apache.org/jira/browse/LANG-1069
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.*
>    Affects Versions: 3.3.2
>            Reporter: Duncan Jones
>            Priority: Minor
>             Fix For: Review Patch
>
>         Attachments: CharSet-1069.patch
>
>
> As discussed in [this Stack Overflow 
> question|http://stackoverflow.com/questions/27070515/how-can-i-include-the-caret-character-in-an-apache-commons-charset],
>  the documentation for {{CharSet.getInstance()}} don't explain clearly how to 
> include the negation character ({{^}}) as a literal character.
> The two solutions suggested in the SO question are:
> {code:java}
> // Add the '^' on its own
> CharSet.getInstance("^", "otherlettershere");
> // Add the '^' as the last character
> CharSet.getInstance("otherlettershere^")
> {code}
> If those are the best options, we should add a line to the Javadoc to 
> indicate this. If there is a better way, clearly that should be documented 
> instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to