I'm not sure how to help you with your Parse::RecDescent problem (I've never used it), but here is a pure-regex solution that I whipped up (half to help, half for fun) for your original problem: 


my $data = join('',<DATA>);
my $quoted_string =
qr/
    "
    (?:
        (?: [^"]* )
        |
        (?: (?<= \\ ) " )
    )*
    "
/x;
my $balenced_brackets =
qr/
    \{
    (?:
        (?> [^{}"] *)
        |
        (??{$quoted_string})
        |
        (??{$balenced_brackets})
    )*
    \}
/x;
my $function_header = qr/ function \s+ \w+ \s* \( [^)]* \) \s* /x;

my @matches = $data =~ /($function_header $balenced_brackets)/gx;
print join("\n\n",@matches);

[download]

It worked with the sample code that you provided, but I have a feeling it will blow up when presented when it encounters something whacky (an unclosed brace, a brace inside quotes, etc). Consider it a preliminary solution :)

Update I added a bit of robustness to consider the case of the unclosed brace, but it now needs  re 'eval'. I also added a bit of explanation... Its still going to blow up on a brace inside quotes, however...

Update: Update: With some better structure, it can now handle brackets in quotes with no problem.

In reply to Re: Rec::Descent Woes - Parsing JavaScript Files and Other Issues by jryan
in thread Rec::Descent Woes - Parsing JavaScript Files and Other Issues by Incognito

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.