Glad you're having a good time! I think you should be able to use it to implement your language's reader but I don't have any actual experience doing so.
I seem to recall that Racket used to come with a combinator parser library. It's been removed but I don't remember why but maybe that could be an indication that it's not a good idea? My library is currently a straight port from Haskell (ie, not idiomatic Racket) so it won't be as nice as the built-in parsing tools in terms of fitting into the Racket toolchain. You may have to do some manual "gluing". A few things off the top of my head: 1) Input-wise the parser combinators only consume strings. To be fully Rackety, they should work with ports (if anyone wants to take a crack at it, it would be very appreciated). 2) You'll have to manually convert the character outputs to syntax. 3) You'll have to manually extract the source location from the parsack state and add it to your syntax objects. Greg Hendershott can probably fill you in on more unpleasantries, as his markdown parser is the biggest client (that I currently know of) :) On Mon, May 11, 2015 at 9:40 PM, Daniel Prager <daniel.a.pra...@gmail.com> wrote: > I've been having a great time playing with Stephen Chang's Parsack > (parsec-style parsing for Racket) and enjoying the straightforward learning > curve and usability. Thanks Stephen! > > Has anyone used Parsack to do the parsing for a little language and then > plugged it into the main Racket infrastructure? > > Good idea? Mismatched tool? What does it / would it take? > > > Thanks > > Dan -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
