You are numbering all abc's. There is no need to match surrounding characters. Note that the way I have rewritten your test cases removes all ambiguity concerning white space.
use strict; use warnings; use Test::More; my @cases = ( # Input Expected Description ["int abc;\n", "int abc_1;\n\nint abc_2;\n\n", 'line 1'], [".abc(abc);\n", ".abc_1(abc_1);\n\n.abc_2(abc_2);\n\n", 'line 2'], ); plan tests => scalar @cases; foreach my $case (@cases) { my $line = $case->[0]; my $out = ''; $out .= ($line =~ s/abc/abc_$_/gr) . "\n" for (1,2); is( $out, $case->[1], $case->[2] ); }
OUTPUT: 1..2 ok 1 - line 1 ok 2 - line 2
Bill

In reply to Re^5: Please correct me in the above regular expression by BillKSmith
in thread Please correct me in the above regular expression by suvendra123

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.