Note that, in fact,
moritz's improved version is essential—without it, your match has the potential to find your replaced text (since the
s/// resets
pos, so that the
//g match starts all over again). For example, if you try your code (even suitably modified) on
$toTranslate = 3 x 33332, then you'll get
[[4]2], not
[33332].
Note also that Perl goes out of its way to make sure that you can do lots of things that seem like they must be multi-step in a single statement. Thus, as moritz implicitly observed, it's probably better to write $tmpFound = length($1) (well, and use a better name) than $tmpFound = $1; $tmpFound = length($tmpFound).
UPDATE: On testing, moritz's version does the same thing. I think that you want something like
my $translated;
while ( $toTranslate =~ /(.*?)((?:3{4})*)/g ) {
$translated .= $1;
$translated .= '[' . length($2) . ']' if $2;
}
UPDATE 2: eye and AnomalousMonk pointed out a better, s///g-based solution: just omit the while.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.