If you completely trust your $outputString not to have anything malicious in it, you could use string eval.

$searchString = '(T)(est).(\d{2}).*';
$outputString = 'This $3 a $1$2';
$sampleData = "Test 22";

$sampleData =~ /$searchString/ && eval qq{print "$outputString"};
print "\n";
__END__
This 22 a Test
[download]

I think, however, this should be considered a last resort.

If I'm not missing something you can generalize the principle to any number of parameters. Parameters you don't need are undef or garbage, but that should not matter

$searchString = "(T)(est).(.{2}).*";
$outputString = 'This $3 a $1$2';
$sampleData = "Test is good";

if ($sample_data =~ m/$search_string/)
{
    say $make_output_string->($1,$2,$3,$4,$5,$6,$7,$8);
}
[download]

You could to this with a little eval magic (see the caveats, later). What I have in mind would be something like the following:

  if( $sampleData =~ /$searchString/ ) {
      print eval qq{"$outputString"};
  }
[download]

The outer qq{} quote is used to generate an evaluateable string by adding double quotes around the original. When evaluated, this new string interpolates your variables into place.

There are a few problems with this approach:

• You may need to escape characters in the string (: at a minimum)
• This is effectively compiled at run-time, which means unexpected errors can result.
• You need to carefully scrub the output strings to prevent injection attacks.

You are basically trusting the incoming string to be safe to evaluate and run as code. This is not always a valid or safe assumption.