addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Parsing - or why regexes are underused in Haskell

Friends of the Functional!

Something nice!
Something handy!
Something beginner-friendly!
An introduction to using `parsec`/`attoparsec`/`aeson`.

- `aeson` is the haskell JSON-parser du jour
- `attoparsec` is a parser combinator that has one thing in mind - speed (at the cost of error messages), can parse `Text` (a.k.a. better Strings) and `ByteString` (a.k.a. binary data)
- `parsec` gives great error messages - guess what it is slower

Some suggestions - please chose - simple attoparsec example (kata - from january)
- We can go through the examples from RealWorldHaskell (PPM, PGM pictures)
- Simple JSON parsing
- XML for the intermediate/advanced Haskellers out there with `conduit`
- your suggestion here

If anybody would like to present comment - I would be fond to have you!

Cheers Martin

Join or login to comment.

10 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy