I can successfully eval a *.csh file in Perl using backticks line-by-line. But I would like a report if eval should fail. In the code below, $@ gives complaints as if the contents of the backticks were Perl code. So even if the eval and backticks both run fine, $@ has needless complaints. Is there a workaround? 
my $os_says = '';
my $pl_says = '';

if ( open FH, '/home/foo/bar.csh' ) {
  while (<FH>) {
    # no warnings;
    eval { $os_says .= `$_` }; # <- Fixed. Thanks Roger!
    if ($@) { $pl_says .= $@ } 
  }
  print "OS says: $os_says \n";
  print "Perl says: $pl_says \n";
}

[download]

Roger fixed this. I had been using parens, not braces, with my eval.

In reply to $@ with backticks inside eval by aplonis

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.