I'd say that you should base your work on Marpa::R2. The problem w/ Marpa::R2 is that there's a lot of legacy stuff, and not a few just plain ol' bad ideas, embodied in the code, so it's very hard to work from. But it *is* stable and works.
Marpa::R3 and Kollos are works in progress. As such, at times they make a dicey basis for my own work, never mind anybody else coming to the code. You might mine them for ideas about where to take the code, but even here, we do change our minds, so we might, for example, advise you to delete a module or feature are unnecessary, only to later realize that it is essential. With Marpa::R2 the feature set may not be ideal, but it is stable and quite useable. The latest Kollos is actually a tiny core of code now inside Marpa::R3. I will probably abandon the older Kollos distribution, mining it for code and ideas. The Kollos distribution and Marpa::R3 at present are alpha and experimental -- no support or stability. Marpa::R3, with the new Kollos being created inside, will probably move to beta and beyond, but that is not happening fast. The older Kollos distribution is a dead end. I hope this helps, jeffrey On Wed, Aug 3, 2016 at 11:42 AM, <[email protected]> wrote: > I'm trying to parse VHDL in a tool I've written in Ruby. I'm interested > in using Marpa for the parsing; I currently have a line-oriented mess of > regex's that work almost all the time for common coding style. > > I've done some reading, but I haven't been able to answer the following > questions. I apologize for asking since I would be surprised if they > aren't already answered *somewhere*. I *have* looked, but Google results > can give such a random walk.... > > * For a project starting fresh (and in beta for a few months at least), > should I be starting with Kollos or Marpa::R2 or Marpa::R3 or something > else? > > * I finally got libmarpa (kollos branch) compiling by itself. I go to the > kollos (master) source, and the HOWTO document has me stymied. Is there a > less terse explanation available for how to compile and use Kollos? > > * Any suggestions on how to bridge from another language (Ruby) to > Lua/Perl is appreciated. I don't think I have time to write new bindings. > I anticipate I'll use some combination of files, sockets, and FFI to cross > the gap. > > FWIW, I wrote an Earley parser from scratch in Ruby. It fun, and it > works, but it's slow. > > -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
