I can't think of any particular reason off the top of my head. I think it may be just that we haven't kept it up to date.
On Fri, Jul 23, 2010 at 2:50 AM, Kevin Jardine <[email protected]> wrote: > Before I work on this, I was wondering about a couple of things: > > - why does Heist use version 0.16 of hexpat instead of the most recent > version (0.18.1) ? > > - I notice that hexpat 0.18.1 shows a build failure under GHC 6.12. Is that > why it is not used? Should I also try to fix the build failure or should I > start by patching hexpat 0.16 to support CDATA and worry about the more > recent version later? > > Kevin > > --- On Thu, 7/22/10, Gregory Collins <[email protected]> wrote: > >> From: Gregory Collins <[email protected]> >> Subject: Re: [Snap Framework] Including javascript in Heist templates >> To: "Kevin Jardine" <[email protected]> >> Cc: [email protected] >> Date: Thursday, July 22, 2010, 10:39 PM >> Kevin Jardine <[email protected]> >> writes: >> >> > Fixing hexpat CDATA support sounds like a doable and >> useful task. >> > >> > I could look at that next week. >> > >> > Do you have some hints / advice to get me going? >> >> It should be easy I think -- extend node type to include >> cdata as well >> as text, re-organize the parser callbacks for cdata to >> generate cdata >> nodes instead of text ones, and fix the output functions to >> re-wrap >> cdata nodes in cdata blocks. I think that should be it. >> Stephen >> Blackheath is the hexpat maintainer, maybe you could >> coordinate with >> him. >> >> G >> -- >> Gregory Collins <[email protected]> >> > > > > _______________________________________________ > Snap mailing list > [email protected] > http://mailman-mail5.webfaction.com/listinfo/snap > _______________________________________________ Snap mailing list [email protected] http://mailman-mail5.webfaction.com/listinfo/snap
