Why not use uu-parsinglib, which will tell you what is wrong and nevertheless will continue parsing?
Currently Jacco Krijnen is working on an extensible version of Pandoc, based on the AspectAG and the Murder packages, so you can define your own plugins for syntax and semantics. Doaitse Swierstra On Aug 1, 2013, at 1:14 , Richard A. O'Keefe <o...@cs.otago.ac.nz> wrote: > > On 31/07/2013, at 8:16 PM, Simon Hengel wrote: >> >> * There is no such thing as a parse error in Markdown, and I think we >> should try to make this true for Haddock markup, too > > It is very far from clear that this is a virtue in Markdown. > In trying to learn Markdown, I found it an excessively tiresome > defect. Whenever I was trying to learn how to produce some > combination of effects, instead of Markdown telling me > "at THIS point you had something I wasn't expecting", it would > just produce incorrect output, defined as "anything other than > what I intended". It also meant that two different Markdown > processors would accept the same text silently but do different > things with it. > > This is one of the reasons I won't use Markdown. > > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
