Re: Is the skip: directive broken in Parse::RecDescent ?

<skip:qr/#\w+/> 'foo' 'bar'
is equivalent to
/(?>#\w+)(?>foo)(?>#\w+)(?>bar)/

/#\w+/ isn't matched by the "#skdjslkdjsakdjadjlksa\n" before "foo" (note the newline).
/#\w+/ isn't matched by the "" before "bar".

I think you want <skip:qr/(?:#\w+\n)?/>

By the way,
/#\w+/ 'foo' 'bar'
is equivalent to
/(?>\s*)(?>#\w+)(?>\s*)(?>foo)(?>\s*)(?>bar)/
since the default skip is /\s*/.

Update: Added "by the way" bit.

Comment on Re: Is the skip: directive broken in Parse::RecDescent ? Select or Download Code

Replies are listed 'Best First'.
Re^2: Is the skip: directive broken in Parse::RecDescent ? by Hercynium (Hermit) on Aug 11, 2008 at 22:01 UTC
Thanks again, ikegami. You've given me another avenue to search for my solution. I'm curious though - the trace shows that the skip block is being treated like a production... and it's returning a value! `[\s*]` Do all modified prefix matches return this, or just skip directives?	[reply] [d/l]
Re^3: Is the skip: directive broken in Parse::RecDescent ? by ikegami (Patriarch) on Aug 11, 2008 at 22:22 UTC
Quote the docs, The `<skip>` directive evaluates to the previous terminal prefix, so it's easy to reinstate a prefix later in a production (Followed by an example)	[reply] [d/l]
Re^4: Is the skip: directive broken in Parse::RecDescent ? by Hercynium (Hermit) on Aug 12, 2008 at 16:02 UTC
Silly me... I think by then my brain was too frazzled to understand the docs! Thanks!	[reply]