Site navigation

StringArray::addTokens() bug!

General JUCE discussion
#1

Look at these examples:

[code]StringArray tokens;

tokens.addTokens(T(“two words”), false);
// tokens.size() is 2 (correct!)

tokens.clear();
tokens.addTokens(T("five words with trailing space "), false);
// tokens.size() is 6 (incorrect!)

tokens.clear();
tokens.addTokens(T("six words with two trailing spaces "), false);
// tokens.size() is 8 (incorrect!)

tokens.clear();
tokens.addTokens(T(" five words with leading space"), false);
// tokens.size() is 6 (incorrect!)

tokens.clear();
tokens.addTokens(T(“seven words with three spaces in middle”), false);
// tokens.size() is 9 (incorrect!)
[/code]

I don’t think we want leading, trailing, and multiple spaces included when tokenizing, do we?

It’s easily handled with a call to StringArray::removeEmptyStrings(true) when tokenizing whitespace, but not as easily remedied when tokenizing with other break characters.

#2

I’d say just use spirit to parse it, would be worlds easier.

Actually, spirit is probobly overkill, boost:tokanizer is made for exactly that kind of thing though, and its been through its paces years ago so there are no known bugs. And it would let you parse tokens based on whitespace or any other seperator. Would work quite well inside addTokens() in the StringArray class.

#3

[quote=“Randy”]Look at these examples:

[code]StringArray tokens;

tokens.addTokens(T(“two words”), false);
// tokens.size() is 2 (correct!)

tokens.clear();
tokens.addTokens(T("five words with trailing space "), false);
// tokens.size() is 6 (incorrect!)

tokens.clear();
tokens.addTokens(T("six words with two trailing spaces "), false);
// tokens.size() is 8 (incorrect!)

tokens.clear();
tokens.addTokens(T(" five words with leading space"), false);
// tokens.size() is 6 (incorrect!)

tokens.clear();
tokens.addTokens(T(“seven words with three spaces in middle”), false);
// tokens.size() is 9 (incorrect!)
[/code]

I don’t think we want leading, trailing, and multiple spaces included when tokenizing, do we?

It’s easily handled with a call to StringArray::removeEmptyStrings(true) when tokenizing whitespace, but not as easily remedied when tokenizing with other break characters.[/quote]

that’s usually true for whitespace, but if I was tokenising with other separators, e.g.

“a,b,c,”

then I’d be quite annoyed if it didn’t return 6 items, three of them empty… And of course removeEmptyStrings would clean this up too, if you just want the non-empty tokens.

#4

[quote=“jules”]that’s usually true for whitespace, but if I was tokenising with other separators, e.g.

“a,b,c,”

then I’d be quite annoyed if it didn’t return 6 items, three of them empty… And of course removeEmptyStrings would clean this up too, if you just want the non-empty tokens.[/quote]

A very good point I’d completely overlooked as I’m only dealing with whitespace! I’ve just thrown in a bunch of removeEmptyStrings() calls into my parsing routines to clean it up.

#5