Instead of using ParseRecDescent, may I suggest a Regexp::Common solution? Parsing lists is one of its options. 
#!/usr/bin/perl

use strict;
use warnings;

use Regexp::Common;

my $re = $RE{list}{-sep => '_'}{-pat => '(?:(?!_)\w)+'};

while (<DATA>) {
    chomp;
    print "'$_' ", /^$re$/ ? "matched\n" : "did not match\n";
}


__DATA__
apple_pear
apple_plum_grape
_
apple
_apple
apple_
apple__pear




'apple_pear' matched
'apple_plum_grape' matched
'_' did not match
'apple' did not match
'_apple' did not match
'apple_' did not match
'apple__pear' did not match

[download]

Abigail

In reply to Re: ParseRecDescent and csv-like data by Abigail-II
in thread ParseRecDescent and csv-like data by rkg

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.