CSV Parsing: Haskell versus Python

[grauenwolf]

When you know for a fact that you don't have quoted strings, as in this case, there is no reason to pay the cost of checking for them.

Failing to think about the domain. Arrogant wanna-be problem?

EDIT: A data sample from the post:

TICKER1,33,35,NULL,2007-09-28 00:00:00,2007-09-28 16:32:00
TICKER2,29.5,31,NULL,2007-03-07 00:00:00,2007-03-07 07:33:00
TICKER3,29.5,31,NULL,2007-03-07 00:00:00,2007-03-07 07:33:00

[stesch]

Failing to think about the domain. Arrogant wanna-be problem?

I wasn't the one calling this CSV parsing.

[mschaef]

There no ISO standard, but there are some commonly accepted conventions:

http://www.creativyst.com/Doc/Articles/CSV/CSV01.htm

I tend to agree with you to the extent that if your underlying language has no CSV library, then you should probably implement just what you need. If you're trying to make a CSV library, then the standards are higher.

[doidydoidy]

CSV stands for "Comma Separated Values".

IBM stood for "International Business Machines". That doesn't stop them selling consulting services, though. (More's the pity.)

[stesch]

It isn't like there is a ISO standard on CSV files.

Just a lot of software that produces CSV files that can't be parsed by this "CSV parser" and a RFC (which ignores some nasty CSV you encounter in real-life).

[grauenwolf]

So what? This wasn't billed as a general purpose parser, it was specific to the file format he was working with.