My experience (at least a year ago) was that fastercsv was a great way
to go if you had very clean files without errors, odd characters,
etc. Unfortunately, I had files that were a bit more problematic and
so I ended up using a combination of either parsing it myself (split,
regexs. etc) and catching all the errors and handling them or using
the parse_line method in the standard csv library.
On Jun 9, 2008, at 2:09 PM, Avdi Grimm wrote:

> On Mon, Jun 9, 2008 at 2:08 PM, Justin To <tekmc@hotmail.com> wrote:
>> So is the fasterCSV the most effective way of parsing a comma-
>> separated
>> file?
>
> It is the fastest and most robust way.
>
> --
> Avdi
>
> Home: http://avdi.org
> Developer Blog: http://avdi.org/devblog/
> Twitter: http://twitter.com/avdi
> Journal: http://avdi.livejournal.com
>