Just to note: since $1 and its ilk will keep their values if the regex fails to match, make sure you wrap this all in a conditional. I'm not sure about what's so bad about using length here; the grouping number shift is going to be a problem anyway, if your code's not setting $regexp, how will you know whether it has groupings at all? (and if so, how many). Of course, if you want to nab those matches, you can always use a nice listy assignment like: 

if (my ($foo, $bar, @reg_groups) = $string =~ /^(.*?)($regexp)/) {
  # $foo = $1, $bar = $2, @reg_groups = all the matching groups from $
+regexp
 my $totength = length $foo.$bar;
 my $foolength = length $foo;

    # whatever happens next
}

[download]

HTH

In reply to Re: Getting information about regexp matches by arturo
in thread Getting information about regexp matches by ariels

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.