Nov. 17, 2011
10:11 a.m.
On 17.11.2011 10:38, Henrik Sperre Johansen wrote:
The efficiency drain in this example is, as Dennis points out, CSVParser adding scanned characters 1 by 1 to the WideString representing current value.
Cheers, Henry
There is something strange going on with CogVM's though, on an old VM the CSVParser use about 17 secs on Data.csv, while it's 131 secs on Cog 2508... It looks like primitive 61 has a *really* slow path for variable word classes? Cheers, Henry