I'm tempted to say that for things like HTML and CSV, the real reason not to use a parser combinator library is that "standard" turns out to mean pretty much nothing whatsoever. And you want to use someone else's battle-tested workarounds developed over years for a "standard format" that's more or less a free-for-all.
On 08/30/2018 03:43 PM, Bardur Arantsson wrote:
> On 30/08/2018 20.21, Olaf Klinke wrote:
>
>>> Hello, Olaf. I have some distrust of elegant solutions (one of
>>> them are C.P. libs).
>>
>> [*] To the parser experts on this list: How much time should
>> a parser take that processes a 50MB, 130000-line text file,
>> extracting 5 values (String, UTCTime, Int, Double) from each line?
>
> Not an expert, but for something as (relatively!) standard
> as CSV, I'd probably go for a specialized solution like
> 'cassava', which seems like it does quite well according to
> https://github.com/haskell-perf/csv
Playing the devil's advocate here....
If parser combinators aren't great for "relatively standard" things
such as CSV, then what *are* they good for?
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.
--