Provides classes and interfaces to handle text.
double
)
equivalent to standard String/Double methods?
With Javolution 4.1, double
formatting/parsing is lossless
and functionally the same as with the standard library. Parsing a character
sequence will always result in the same number whether it is performed with
{@link javolution.text.TypeFormat TypeFormat} or using Double.parseDouble(String))
.
When formatting a double
number, the number of digits output
is adjustable. The default (if the number of digits is unspecified) is 17
or 16
when the the 16 digits representation can be parsed back to
the same double
(mimic the standard library formatting).
Javolution parsing/formatting do not generate garbage and has no adverse
effect on GC. Better, it does not force the user to create intermediate String
objects, any CharSequence/Appendable
can be used! Serial parsing is also supported
(cursor parameter).
It all depends of the size of the text to append (the actual size of the document being appended has almost no impact in both cases).
If the text being appended is large (or arbitrarily large) then using {@link javolution.text.Text Text} is preferable.[code] class FastCollection { public final Text toText() { // We don't know the length of the text representation for // the collection's elements, we use Text concatenation // to avoid copying what could be quite large. Text text = Text.valueOf("{"); for (Record r = head(), end = tail(); (r = r.getNext()) != end;) { text = text.plus(valueOf(r)); if (r.getNext() != end) { text = text.plus(", "); } } return text.plus("}"); } }[/code] When appending small text (e.g. < 20 characters) then {@link javolution.text.TextBuilder TextBuilder} works faster. class Complex { double real, imaginary; public Text toText() { TextBuilder tmp = TextBuilder.newInstance(); try { tmp.append(real).append(" + ").append(imaginary).append("i"); return tmp.toText(); } finally { TextBuilder.recycle(tmp); } } }[/code]
"/proj/lodecase/src/com/lodecase/util/foo.java"
, and
"/proj/lodecase/src/com/lodecase/util/bar.java"
.
Can the 'Text' class save us memory when strings
have common prefixes?
It depends how you build your text. For example in following code:[code]
Text directoryName = Text.valueOf("/proj/lodecase/src/com/lodecase/util/");
Text fooFileName = directoryName.plus("foo.java");
Text barFileName = directoryName.plus("bar.java");[/code]
The prefix (directoryName)is shared between fooFileName
and barFileName
.
Text is a binary tree of blocks of characters. In the example,
above, fooFileName
is a node with directoryName
for
head and "foo.java" for tail. The tree is maintained balanced automatically
through tree rotations.