You're on the right track, but you need to know about the -e command line switch (try reading man perlrun). So you'll do something like this: 
my $result = qx/ perl -cw -e '$code' 2>&1/;

[download]
Where you'll then need to scrape the $result string to find out if it passed or failed.

There's another angle to the problem though, you'll need to run the $code through some sort of shell quoting routine, to make sure you don't confuse the shell with characters in perl that also happen to be significant to the shell. I think the cpan module String::ShellQuote works okay for this.

(Note: updated, stealing a hint from shmem to append 2>&1 to the command, this makes sure you'll capture error messages to $result.)

In reply to Re: How to do a "perl -c(w)" check instead of an "eval $string" on a code string by doom
in thread How to do a "perl -c(w)" check instead of an "eval $string" on a code string by Your Mother

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.