BrowserUk:

I've been meaning to follow up on this post for some time, but was recently strapped for 'round tuits'. I don't think you wrote it badly, more like I just disagreed. The followup I was going to post was a set of reasons that it's a good idea to split the lexer and parser into different sections. However, with the new additions to Marpa, I'm rather hard pressed to think of a good reason. ;^)

I don't know if you've been following Marpa::R2, but they've been going in the direction of putting tokenizer rules in the grammar, and it looks rather good. If I were to start over on my project, I think I'd do it that way. (In fact, I've been migrating toward the scanless grammar, I just haven't moved my tokenization in there yet. I'm currently working on getting some of the semantic actions worked out. (As you can tell from the time between posts, this is just a side project, and I've not been working terribly hard on it of late.)

So if you're still working on your project where you need a good parser engine--or are going to start another--I'd encourage you play with Marpa for a couple of hours to see if it works well for you.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re^11: Block-structured language parsing using a Perl module? by roboticus
in thread Block-structured language parsing using a Perl module? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.