Hello: Perhaps the Javadoc could mention when to use a StrMatcher vs RE's in 1.4 or Jakarta's ORO.
I would say that removing any code duplication is key in this on-going refactoring. So I look forward to seeing the complete refactoring. I also have a (fantasy?) goal that we could get 100% unit test coverage for the new text package. ;-) Gary > -----Original Message----- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 14, 2005 3:03 PM > To: Jakarta Commons Developers List > Subject: [lang] StrMatcher in text subpackage > > I have now performed the first step in unifying the disparate text > subpackage, creating a top-level StrMatcher class. > > StrMatcher is extracted from StrTokenizer and tidied up. It provides a > way of searching a character buffer for a match. Basic matchers do > nothing interesting, but user-written subclasses could. > > So far, it's only used in StrBuilder, where indexOf, lastIndexOf, > contains, delete and replace all have variants that take a StrMatcher now. > > The next step, unless there are objections, is to refactor StrTokenizer > to use the new StrMatcher class (rather than the old one still inside > it). Then methods can be added to StrBuilder such as split() and > tokenizer(). > > Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
