Re:Why I prefer scheme to Haskell
by ericssmith on Monday April 09, 2012 @04:24PM
(#3819039)
I use hexpat and it works nicely. I wasn't able to get very far with either haxml or hxt before having grief.
[ Parent
| on HN ]
Re:Why I prefer scheme to Haskell
by egonschiele on Tuesday April 10, 2012 @05:32PM
(#3824555)
I use HXT to parse HTML. AFAICT, Hexpat doesn't do much besides parse the XML file into a tree. It doesn't have the niceties that Nokogiri or BeautifulSoup do. For example, I can use Nokogiri to get all the links on a page like so: page.css("a").
HXT allows me to come close to this:
tree >>> getXPathTreesInDoc "//a"
But I haven't seen a single Haskell XML parsing library that is as nice as Nokogiri.
Re:Why I prefer scheme to Haskell
by ericssmith on Tuesday April 10, 2012 @06:46PM
(#3824885)
In my work, I read in XML, parse its elements, attributes, and data, producing new XML. Along with Parsec, Hexpat is well-suited to the task.
I haven't had to parse HTML in Haskell. I use BeautifulSoup for that. I wouldn't be surprised if the Haskell libraries aren't as useful for that kind of thing.
Re:Why I prefer scheme to Haskell
by egonschiele on Monday April 16, 2012 @04:29AM
(#3846505)
I wrote up a guide to working with HTML in HXT: http://adit.io/posts/2012-04-14-working_with_HTML_in_haskell...
You might find it handy if you decide to give HXT another go :)
Re:Why I prefer scheme to Haskell
by reddit_clone on Monday April 09, 2012 @09:01PM
(#3820152)
Does hexpat work on Windows?
I am asking since it is linking to expat dynamic library..