I'm building it too right now.
|Saizan||ivanm: actually i wouldn't worry of it being a Integer|
|ivanm||Saizan: it was just trying to get rid of the warnings from -Wall, that's all... trying to get my code warning free! ;)|
|syntaxfree||Maybe I should go hack up the other part of the program, but I'm not sure what data structure to begin with for the DOT compilation. I'd need to know what HXT spits out.|
|Cale||syntaxfree: anything that you like.|
Basically, it'll probably give you a title and list of URLs.
|syntaxfree||Intuition says, "start from Map Title [URL]".|
oh cool. That's basically what I need.
|Cale||haha, gcc is eating almost 300MB compiling this file.|
|syntaxfree||here it's eating a measly 139MB.|
|Cale||XmlDTDParser was pretty large|
Now it dropped to 22.
|vincenz||Anyone know anything about Ivor?|
|syntaxfree||hmm. I saw a GetHTTP module fly by in HXT.|
does it handle that part?
|action||earthy grumbles at compiling wxHaskell with profiling support|
|earthy||grumbles at compiling wxHaskell with profiling support|
|earthy||wxHaskell *really* *NEEDS* to be cabalized|
|syntaxfree||oh cool. I was already reading the Network.HTTP docs|
|Cale||syntaxfree: You can pass it a filename or a URL and it'll just handle that.|
|syntaxfree||that sure makes my job easier.|
Maybe I should switch to some Haskell graph structure.
and write a generic Haskell graph -> DOT file processor.
|Cale||It's a really cool library, it just needs some paring down in places, and the documentation needs more organisation.|
|edwinb||vincenz: I know a little about it|
|vincenz||edwinb: how does it compare to other such frameworks as I had never heard of it before, and it's based on a separate parser, cause the webpage mentions an interface to be used from haskell|
|edwinb||vincenz: interesting question... I suppose the most similar thing would be Coq|
The main difference is that coq has several man years of development behind it ;)
The advantage of Ivor from my PoV though is that it's easy for me to embed domain specific tactics in a Haskell program, and that I'm free to mess about with the type theory
|action||vincenz nods at edwinb|
|vincenz||nods at edwinb|
|edwinb||for example, it was really useful to be able to add dependent pattern matching|
|vincenz||why a separate language?|
why not a combinator-based approach
|edwinb||there are combinators for making tactics, if that's what you mean|
the separate language is because it can be handy just to write the program text directly
|vincenz||I mean to fully embed it within haskell as a DSL instead of having a parser|
|edwinb||just seems to me that if you can make something a library, then you should...|