Why not just use one hash, the key is the function name and the argument is an array consisting of search regex and replacement. Something like the following: 
use constant SEARCH => 0;
use constant REPLACE => 1;

my %translate = (
  funca => [ qr/funca\( ([^,]+) , ([^,]+) ,([^,]+) ,([^)]+) \)/x,
             '"func($1,$2,XXX,YYY,$4)"' ],
  funcb => [ qr/funcb\( ([^,]+) , ([^,]+) ,([^,]+) ,([^)]+) \)/x,
             '"func($1,$2,,,$4)"' ],
);

while (<DATA>) {
    for my $key (keys %translate) {
        if (/$key/) {
            s/$translate{$key}->[SEARCH]/$translate{$key}->[REPLACE]/e
+e;
            print;
        }
    }
}

__DATA__
funca(10,20,30,40)
funcb(10,20,30,40)

[download]
Of course you might have to adjust the regexes a bit, taking care of whitespace, ... but I think you get the idea.

-- Hofmator

In reply to Re: translate arglist by Hofmator
in thread translate arglist by Anonymous Monk

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.