since the next match blends into the first one

Actually it doesn't.

use strict; use warnings; use Test::More tests => 2; my $pos = match_positions ('GCTTCTTGC', 'AGCTTCTTGCGCTTCTT'); is ($pos, '2 9 ', 'Matched'); # This fails because you have only one o +ccurrence. $pos = match_positions ('GCG', 'AGCGCGT'); is ($pos, '2 4 ', 'Matched'); sub match_positions { my ($regexp, $sequence) = @_; my @positions = ( ); while ( $sequence =~ m/$regexp/ig ) { my $newpos = pos($sequence) - length($&) + 1; push @positions, $newpos; pos($sequence) = $newpos; } return "@positions "; }

Update: fixed the test count to include the second easier-to-follow example.


In reply to Re: Double check for positions by hippo
in thread Double check for positions by bisimen

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.