Its just avoiding grep; again a trivial soln.

cool, I know that u r c00l and all, but could u plz stop im-talking? Many find it plain annoying and it hinders communication between people here. It is appropriate where it is appropriate, that is in IMs et simila, in which case your primary goal is speed and not clarity. But here it's just the opposite.

my $x=1;
foreach(@arr){print  $x++ if (/foo/)}
[download]

Initialization and "efficiency" issues apart, which were duly pointed out by davido, just reasoning solely in terms of user interaction, what benefit could come of incrementally printing the counter at each iteration? You're only interested in the final value anyway. Not to mention the /foo/ gotcha mentioned several times in this thread.

But it can be done using spl variable of reg ex also, if I am right?? Any takers?

cool, I know that u r c00l and all, but could u plz stop im-talking?

my $str=join ' ',@arr;
[download]

That is just like my $str="@arr"; that is, unless you've changed $". And if you haven't then it's a very convenient idiom. If you have, then you should have done so locally in a block anyway, unless yours is a very very special situation.

$str=~ /foo/;
[download]

That is just like "@arr" =~ /foo/; no need for an intermediate variable.

print $&; #### In place of $&; we can use that for no
          #### for no. of matches.
[download]

I understand what you mean, but:

• your match is not a global one (you have to use the /g modifier for that), so the number of matches will always be at most one;
• no, there's not such a variable and no need for it, since a match in global context will return the list of all the matches (or of all the captures if capturing parens are there) and one can use that list in scalar context to get the number of them.