by John Porter >> Wed, 8 Dec 1999 23:38:28 GMT
Ok, I wrote the C++ equivalent (MS Visual C++ 6.0) and timed it.
You can't pass a StringArray to an external method, so I had to
change the test slightly, to return strings instead. In this report,
the convertCsv routines all have the csv string and an integer
starting position (pos) as input, and a string as output. The
routines update pos, and the caller keeps calling until pos goes negative.
In order to be a fair comparison with what I published before, I
modified the best result from last time to actually use the data
returned (move it to a local string). As it turns out, it is fairly expensive to get the data back out of the array.
The best result from last time was 3.92ms per rep. Modifying the test
to use the data returned increased the time to 6.23ms.
I modified the convertCsv method to return an item at a time. Again,
the caller moves each returned string to a local string. The result
was 2.95ms to gather and use the data, so eliminating the StringArray
cut the pure Jade time in half.
The C++ routine, as expected, was the clear winner, taking only
0.51ms per repetition (including the Jade driver script) to parse and
use the data.
All sources are available upon request.
Is there a standard for csv files? Are null strings allowed? What
about embedded quotes? Spaces around the commas? Anybody have this info?
Cheers,
John P