I'd suggest separating parsing from evaluation. The first argument to the action subroutines is a hash that you can use for any purpose. In this case, I'd store parts of the specification in there, then return that hash (which makes the convenient default ::= action => ::first work for the Dice_Expression rule). Also, I split modifier_r_comp from modifier_r action, but you could equally merge them and count the number of arguments. 

use Marpa::R2;
use Data::Dump;

my $dsl = <<'END_OF_DSL';

:default ::= action => ::first
lexeme default = latm => 1

Dice_Expression ::= Dice_Expression1
                  | Dice_Expression1 add_modifier

Dice_Expression1 ::= Simple_Dice
                   | Simple_Dice x_modifier
                   | Simple_Dice r_modifier

Simple_Dice  ::= Rolls 'd' Sides                         action => sim
+ple_roll
add_modifier ::= '+' Die_Modifier_Val                    action => mod
+ifier_add
               | '-' Die_Modifier_Val                    action => mod
+ifier_add
x_modifier   ::= 'x' Die_Modifier_Val                    action => mod
+ifier_x
r_modifier   ::= 'r' Die_Modifier_Val                    action => mod
+ifier_r
               | 'r' Die_Modifier_Comp Die_Modifier_Val  action => mod
+ifier_r_comp


Die_Modifier_Val ~ digits
Die_Modifier_Comp ~ 'gt' | 'lt'

Rolls ~ digits
Sides ~ digits

digits ~ [\d]+

:discard ~ whitespace
whitespace ~ [\s]+
END_OF_DSL

my $grammar = Marpa::R2::Scanless::G->new( { source => \$dsl } );
my $input = $ARGV[0] // '6d4x1';
my $parsed = $grammar->parse( \$input, 'My_Actions' );
print "\n\nParsed result: ";dd $parsed;

# print "\n\nFinal result: ";dd evaluate_rolls($parsed);

sub evaluate_rolls {
    my $spec = shift;
    # TODO...
}

sub My_Actions::modifier_add {
    my ( $self, $sign, $val ) = @_;
    $$self{add} = 0 + "$sign$val";
    $self;
}

sub My_Actions::modifier_r {
    my ( $self, undef, $reroll ) = @_;
    $$self{r} = $reroll;
    return $self;
}

sub My_Actions::modifier_r_comp {
    my ( $self, undef, $comp, $reroll ) = @_;
    $$self{comp} = $comp;
    $$self{r} = $reroll;
    return $self;
}

sub My_Actions::simple_roll {
    my ( $self, $rolls, undef, $sides ) = @_;
    $$self{rolls} = $rolls;
    $$self{sides} = $sides;
    return $self;
}

sub My_Actions::modifier_x {
    my ( $self, $modifier, $modifier_val ) = @_;
    $$self{x} = $modifier_val;
    return $self;
}

[download]

Update: Added +/- modifiers

Good Day,
    Dean

In reply to Re: First steps with Marpa::R2 and BNF by duelafn
in thread First steps with Marpa::R2 and BNF by Discipulus

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.