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
On 31/07/13 06:37, Roman Cheplyaka wrote:
Hi Mateusz,
This looks great — I'm especially excited about List entries no longer
have to be separated by empty lines!
Glad to hear that.
However, the decision to use Attoparsec (instead of Parsec, say) strikes
me as a bit odd,
Parsec has a
Is Data.Text as an extra dependency really that bad? Remember that you
are parsing comments, prose, human produced text, where Data.Text is way
more useful than ByteString.
--
Mats Rauhala
MasseR
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
On 31/07/13 08:21, Mats Rauhala wrote:
Is Data.Text as an extra dependency really that bad? Remember that you
are parsing comments, prose, human produced text, where Data.Text is way
more useful than ByteString.
It has to come with GHC boot packages and it currently doesn't. I have
updated my
Hi Roman,
However, the decision to use Attoparsec (instead of Parsec, say)
strikes me as a bit odd, as it wasn't intended for parsing source
code. In particular, I'm concerned with error messages this parser
would produce.
In addition to what Mateusz already said, I want to briefly summarize
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
Greetings cafe,
As some of you might know, I'm hacking on Haddock as part of Google
Summer of Code. I was recently advised to create a blog and document
some of what I have been doing recently. You can find the blog at [1] if
you're interested. The first post goes over the work from the last
Hi Mateusz,
This looks great — I'm especially excited about List entries no longer
have to be separated by empty lines!
However, the decision to use Attoparsec (instead of Parsec, say) strikes
me as a bit odd, as it wasn't intended for parsing source code. In
particular, I'm concerned with error
