I'm not able to replicate your error; however, there are a few errors/potential errors in your code (at least as written).

In the array of keywords, the comma is wrong unless you mean it to be part of the pattern. "use warnings" catches this.

If you're using lexical variables, $x and @a need a "my" in front of them when declared. "use strict" catches this.

Here's the code with these corrections, and with strict and warnings turned on. It works on my system, but then again, so does the uncorrected code.

#!/usr/bin/perl
use strict;
use warnings;

my @a = qw(xyz uvw tid bnjuw);
foreach my $k ( @a) {
           my $name = $k."\*";
           my $x = `find . -name "$name" -print`;
}

[download]
for(split(" ","tsuJ rehtonA lreP rekcaH")){print reverse . " "}print "\b.\n";

In reply to Re: passing a variable value to Unix command by pobocks
in thread passing a variable value to Unix command by Anonymous Monk

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.