String Parser Trouble

[Burfelt]

I was going to use String Parser object to sort some data for me, but it seems it keeps crashing my app.
I've taken everything apart and it looks like there is a problem with "sort elements ascending"?

I've uploaded my problem here www.inventiveminds.dk/StringParser_error.zip
I'd be grateful if someone could confirm that there is a bug in the object or simply tell me if I'm not using it right.

[Nifflas]

By the look of your example, it definitely appears to be a string parser bug. An option is to use Jamie's String Tokenizer, and using the list object to sort the data.

[SEELE]

I doubt you were looking for a fix, but here is one anyway :GRIN:
http://rapidshare.com/files/102478389/StringParser_fix.mfa.html

[Nifflas]

That's a clever workaround. Personally, I'm so paranoid that if an extension even once causes a crash when it shouldn't, I instantly replace it with another.

[DanielRehn]

I'm just like you then Nifflas, I also replace it... Just to make sure that it wont cause any other "random" problems or crashes!

[Benicle]

I would, except the string parser is too useful for me to go without.

[Burfelt]

Thanks for your input guys.
SEELE: I was going for that exact work around, execpt there are still issues.

Again I've cut it down to a few events. If anyone could take a look at this it would be much appreciated.

It seems you can't delete one element at a time? When the string is just 2 elements long it deletes both of them? Another bug?

www.inventiveminds.dk/string_parser_quirk.zip

[Nifflas]

I would, except the string parser is too useful for me to go without.

It is useful, but when it comes to plain and simple string tokenization, I can't still believe that people add the String Parser instead of Jamie's String Tokenizer.

[Benicle]

I do use Jamie's when it's a simple tokenizing job, most of the stuff I do isn't though.

[Nifflas]

Thanks for your input guys.
SEELE: I was going for that exact work around, execpt there are still issues.

Again I've cut it down to a few events. If anyone could take a look at this it would be much appreciated.

It seems you can't delete one element at a time? When the string is just 2 elements long it deletes both of them? Another bug?

http://www.inventiveminds.dk/string_parser_quirk.zip

That looks like another string parser bug to me. I couldn't find another explanation.

Perhaps we need an updated string parser with the bugs solved, or even an replacement extension that makes more sense (0-based, etc.)? It's somewhat scary to add an extension to your application when you know it do have bugs...