hi,
use strict; + use warnings; + use autodie; + my @test_svc = ( "test\@customer1.service", "test\@customer2.service", "test\@custome3.service", "test\@customer4.service", "test\@customer5.service", "test\@customer6.service", ); my @customers = qw/ customer1 customer2 customer33 customer4 customer5 + /; for my $cust (@customers) { if ( my ( $matched ) = grep $_ =~ $cust, @test_svc ) { print "$cust matches:\t $matched\n"; } else { "no matches for $cust\n"; } }
When I run it:
$ perl /tmp/kk.pl Useless use of string in void context at /tmp/kk.pl line 38. customer1 matches: test@customer1.service customer2 matches: test@customer2.service customer4 matches: test@customer4.service customer5 matches: test@customer5.service
So it correctly sees the matches, but I miss the mismatch. What is wrong with my crappy script? ;-)

TIA.


In reply to Useless use of string in void context at by natxo

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.