[LANG] - Meaning of 'Complete new Tokenizer Class'

["Harrington, James MAJ" <ja...@tb12.arfor.army.mil>]

Hi,

 

I was going to take a stab at this task on the LANG list, but thought
I'd better ask a few questions first.  First, I can think of three
possibilities for a string tokenizer implementation in LANG:

 

- a new implementation for the interface presented by
org.apache.commons.lang.text.StrTokenizer

- a new implementation for the interface presented by
java.util.StringTokenizer

- an implementation of an interface representing the most commonly used
features of string tokenizers

 

I would define those most commonly used features as being those
implemented by jave.util.StringTokenizer minus the ability to change
delimiters plus the concept of 'quoted' test from
org.apache.commons.lang.text.StrTokenizer.

 

Second, is there other alternatives that I haven't thought of?

 

I would suggest the third option above, but mostly I wanted to find out
which direction is desired.

 

Thanks,

 

  Jim

 

 

Re: [LANG] - Meaning of 'Complete new Tokenizer Class'

[Stephen Colebourne <sc...@btopenworld.com>]

Harrington, James MAJ wrote:
> I was going to take a stab at this task on the LANG list, but thought
> I'd better ask a few questions first.  First, I can think of three
> possibilities for a string tokenizer implementation in LANG:
> 
> - a new implementation for the interface presented by
> org.apache.commons.lang.text.StrTokenizer
> 
> - a new implementation for the interface presented by
> java.util.StringTokenizer
> 
> - an implementation of an interface representing the most commonly used
> features of string tokenizers

Asking on the list is definitely a good idea before coding excessively :-)

Where did you get the quote in the subject line?

I would say based on my review of StrTokenizer tonight that it has all 
the right methods and looks about complete. However it may not be fully 
tested, and that may be the task to do.

Also in this package, StrBuilder is complete, with the possible 
exception of adding a subBuilder() method to allow operations on a range 
of the builder. But that is quite complex to write and test.

VariableFormatter needs the most work and had outstanding patches in 
various places.

Stephen




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