comment on

Ah, you are completely right about \N, of course. I'm just a blockhead ;(

Concerning quotes: I think that the way I structured mine is easier to convert from logic. For instance, I defined a quoted string as:

- start quote
- string of (non-quote or backslashed quote) characters
- end quote
[download]

Which I then translated into (comments added this time):

rule quoted_string
{
    " # start quote

    [ # string
    
        <-["]>+: # non quote characters
        | # or 
        [ <after \\ > " ] # backslashed quote character

    ]* # end string

    " # end quote
}
[download]

It was then shown how to make it "dynamic" by simply adding an argument and subsituting that argument in for the quote delimeter. While yours is much more elegant and efficient, I thought that my example was easier to follow in the current context.

In reply to Re: Re: Parsing with Perl 6 by jryan
in thread Parsing with Perl 6 by jryan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks