That design requires advance knowledge of the script (to change $1 to the parameter). I don't know if that's a problem.

The implementation fails if $param contains two spaces in a row, a quote, etc due to improper encoding of strings. Fix: 

sub to_sh_lit {
   my ($s) = @_;
   die if !utf8::downgrade($s, 1);  # Expecting bytes.
   die if $s =~ /\x00/;             # NUL can't be passed.
   $s =~ s/('+)/'"$1"'/g;
   return "'$s'";
}

my $lit_param = to_sh_lit($param);
print SH "echo $lit_param\n";

[download]

Update: Added code.

In reply to Re^2: Running Entire Bash Script Inside Perl by ikegami
in thread Running Entire Bash Script Inside Perl by bichonfrise74

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.