> > Any plans to decouple the parsing combinators (more importantly the > error messages/position tracking) from parsing text? "A seqable > object" as in the second argument to parse is not necessarily > something for which lines and columns make sense. > > Not yet. I've decided that first the library must get really good at parsing text. Once I have more experience writing and using this library, that'd be a good goal to have. But for now it's about text.
Or to make your parser an honest monad (i.e. to implement the > algo.monads interface)? > > I have my own project for monoids, functors and monads, based on protocols, which I think is much faster than algo.monads, yet I decided against implementing Kern with a monad transformer for performance reasons. Furthermore, though I think algo.monads it's pretty good, I don't believe it's been so widely adopted as to require Kern users to learn it and use it to structure their own programs. The fact that Kern is monadic is to be transparent to its users. > -- > Ben Wolfson > "Human kind has used its intelligence to vary the flavour of drinks, > which may be sweet, aromatic, fermented or spirit-based. ... Family > and social life also offer numerous other occasions to consume drinks > for pleasure." [Larousse, "Drink" entry] > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
