http://twoguysarguing.wordpress.com/2010/11/11/porting-haskells-parsec/ colorful back and forth from two highly opinionated programmers Fri, 17 May 2013 10:05:20 +0000 hourly 1 http://wordpress.com/ http://twoguysarguing.wordpress.com/2010/11/11/porting-haskells-parsec/#comment-678 Mon, 16 Jul 2012 21:57:54 +0000 http://twoguysarguing.wordpress.com/?p=1077#comment-678 Parse-EZ provides similar (and more) functionality and is a straight forward implementation (no monads, etc.), but is not functionally “pure”. https://github.com/protoflex/parse-ez/blob/master/README.md

]]> http://twoguysarguing.wordpress.com/2010/11/11/porting-haskells-parsec/#comment-673 Fri, 18 May 2012 15:13:54 +0000 http://twoguysarguing.wordpress.com/?p=1077#comment-673 My implementation does currently leak stack, I’ll grant you that. Pile enough combinators together and eventually you’ll get a StackOverflowException. Others have noticed that and there is working ongoing to fix the situation, but were you referring to leaking memory by using continuations?

]]> http://twoguysarguing.wordpress.com/2010/11/11/porting-haskells-parsec/#comment-672 Fri, 18 May 2012 04:30:22 +0000 http://twoguysarguing.wordpress.com/?p=1077#comment-672 It seem to me that by introducing continuations you reintroduce the space leaks that the original Parsec implementation tries to avoid so hard.

]]> http://twoguysarguing.wordpress.com/2010/11/11/porting-haskells-parsec/#comment-367 Mon, 22 Nov 2010 00:13:46 +0000 http://twoguysarguing.wordpress.com/?p=1077#comment-367 [...] Porting Haskell’s Parsec « Two Guys Arguing (tags: clojure parsing haskell continuations) [...]

]]>