commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33889] - [lang] split camel case strings
Date Fri, 21 Apr 2006 23:47:40 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33889>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33889





------- Additional Comments From bayard@apache.org  2006-04-21 23:47 -------
That's a good point Matt. Even with the char class, it would only be able to make foo200Bar
be one of:

(foo, 2, 0, 0, Bar)
(foo200, Bar)

It wouldn't be able to give you:

(foo, 200Bar)

Not a big worry for me, but what about "XMLHttpSOAPRequest". That should be split to be (XML,
Http, 
SOAP, Request). So in addition to a char-class to make it more generic, it would need to define
whether 
it considered an immediate repeat to be sticky or not. Starting to sound like (another) StringTokenizer

at that point, but with the tokens being inclusive in the data not exclusive.

So -1 to my generic suggestion, we already have it, either the new text.StrTokenizer, or regular

expressions.

On the particular issue of have a camel case parser, it'd be interesting to implement this
as an instance 
of StrTokenizer. I suspect we'd have to improve the API to allow inclusive tokens.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message