> I've thought about writing an article for The Monad Reader - moving > from Graham Hutton's parsers to Parsec, if there's any interest I'll > look into doing it. For the time being the main difference is probably > that Parsec parsers generally use the TokenParser module for some of > the combinators that Parselib provides directly. Using the TokenParser > module requires a couple of tricks - import it qualified and re-define > unqualified versions of the parsers you need - int, symbol, identifier > - etc. >
I'd like a comparison of how to do similar things in Parsec and uu-parsinglib and polyparse and whatever other parser combinator library you want to throw in. I imagine a sort of cookbook, so that once you have become comfortable with one, you can reference this cookbook to figure out the similarities/differences with another. Also, here's something to add to the thread: I wrote a wrapper module for uu-parsinglib for the functional programming course at Utrecht. The goal was threefold: 1. Support the nice functionality of uu-parsinglib (e.g. error handling, efficiency) while simplifying the interface for beginner programmers, 2. Provide an interface very similar to Parselib which was covered in the course, and 3. Add documentation which was sorely missing from uu-parsinglib. The file (licensed to the public domain) is attached. Regards, Sean
UUParsingSimple.hs
Description: Binary data
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
