>Hi Rick,
>
>Thanks for your great contributions here!
>
>As I expect a few of us here, I find it difficult to grasp how we can make an effective use of these functions. But, sure, with this great feedback, I feel I'll get a hand on it. And I look forward to try to improve some of my string intensive code with it. Not so many examples here. VFP strings are indeed already decently fast.

Tamar Granor mentioned running benchmarks on VFP strings, and Rick Strahl too. If they have their original code we could do newer benchmarks.

>However there's one bottleneck to-day in terms of text handling I often bump into: "csv file upload". I wonder if I am alone here. Do you feel that we could take advantage of the faststring libray to turbo-charge this kind of stuff ? In one way or another.

I'm not sure what you mean.

I've always wanted a CSV class that would let me add rows, access data by the equivalent of a RECNO() and by field names or numbers. Might be interesting to have a FCSV() function which is a cross between FFILETOSTR() and something like a multi-row FALINES(), in that it creates a map into the CSV data that can be accessed easily by row and column / field name. You could add to it, delete from it, operate on it basically like a table.

FCSV_LOAD(cCsvPathname)
FCSV_GOTO()
FCSV_SKIP()
FCSV_RECNO()
FCSV_RECCOUNT()
FCSV_BOF()
FCSV_EOF()
FCSV_APPEND_BLANK()
FCSV_REPLACE()
FCSV_DELETE()
FCSV_RECALL()
FCSV_PACK()
FCSV_ZAP()
FCSV_SAVE(cNewCsvPathname[, column list])
FCSV_COPY_TO_CURSOR(cAliasName)
FCSV_APPEND_FROM_CURSOR(cAliasName)

Something like that ... have always wanted that. Not in version 1. :-)