in reply to Re^3: How to grab Parse::RecDescent error output in a variable?
in thread How to grab Parse::RecDescent error output in a variable?

The reason local breaks it is that local replaces the variable in that lexical scope, and the references to P::RD::ERROR in P/RD.pm are outside the lexical scope of the local invocation (I think).

It's an interesting question though, and IMO the right solution would be to get a patch committed for P::RD that allows the user to specify an alternative filehandle for error output.

Replies are listed 'Best First'.
Re^5: How to grab Parse::RecDescent error output in a variable?
by vrk (Chaplain) on Sep 17, 2008 at 08:21 UTC

    Done, and also received feedback already! Here's the bug report: https://rt.cpan.org/Ticket/Display.html?id=39323

    And here's the solution I was seeking, based on demo/demo_errors.pl: 

    use strict;
use Data::Dumper;
use Parse::RecDescent;

# Simple Lisp S-expressions (as an example)
my $grammar = q#
    start: expression(s?)
         | { die join("\n", map { $_->[0] } @{ $thisparser->{errors} }
+)."\n" }

    expression: /\w+/ 
              | '(' expression(s?) ')'
                { $item[2] }
              | <error>
#;

my $p = Parse::RecDescent->new($grammar);
# This will die if there is an error.
print Dumper($p->start('(foo (bar))'));

# Like so:
$p->start('(foo');

    [download]

    --
    say "Just Another Perl Hacker";

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom