So `xml-conduit` basically rolls its own XML parser. My advice is that
if you don't need validations and you want to keep dependencies small
then you may want to roll the minimal XML parser you need using
`pipes-attoparsec` as a short-term solution.
Right now my main priority is polishing up the `pipes-text` package,
followed by my `rcpl` package. After that, though, then I can begin
working on a `pipes-xml`. Even then it may take me a couple of months
to complete, mainly because XML is difficult to get 100% right and I try
to avoid releasing incomplete libraries to lighten my maintenance load.
On 02/06/2014 10:33 PM, Rodlogic wrote:
I have been using pipes-http for the past few days and I am now at a
point where I need to parse xml responses. I don't need validations
and I don't need to parse the XML into a DOM but instead would like to
parse it directly into my own data structures (a la what existing JSON
parsers are doing in Haskell). And of course, sane dependencies is
also important.
Is there an existing lightweight xml parsing package that I could use
with pipes? If not, does it make sense to build one using pipes-parse?
I am somewhat new to Haskell, so any pointers are well appreciated.
thanks!
--
You received this message because you are subscribed to the Google
Groups "Haskell Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
--
You received this message because you are subscribed to the Google Groups "Haskell
Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
