| Message: 44617 |
 |
BY: James Gray (bbazzarrakk) DATE: 2008-02-21 20:09 SUBJECT: RE: Parsing *large* malformed CSVs You have identified the problem. There are certain situations that cause FasterCSV to look very far ahead before it can be sure of the problem. In the specific one you call attention to, FasterCSV could fail faster. However, there are many edge cases where you cannot, because of the way CSV is designed.
I think the moral is that FasterCSV expects well-formed CSV content. I'm a little cautious of putting in much effort to catch cases like this (slowing it down as I do), when it's impossible to catch them all.
I hope that makes sense.
| |