Why not just send the code straight to "perl -cw" itself? 
sub test_code {
   my $code_to_check = shift;

   my $pid = open(PERL, "|-");
   if (!$pid) {
      die "fork: $!" unless defined $pid;
      exec("/usr/bin/perl", "-cw") or die "/usr/bin/perl: $!";
   }

   print PERL $code_to_check;
   close(PERL);

   return !$?;     # $? == 0 means compile succeeded
}

[download]
You may want to close STDIN/STDERR to handle any output the forked Perl process gives, and just rely on the exit status, or use open2/open3 if you want to capture the compilation messages Perl gives you.

In reply to Re: Syntax Error Checking by Fastolfe
in thread Syntax Error Checking by madhatter

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.