It has nothing specifically to do with POSTMATCH, you just ran into the multi-concatenation optimization.
#!/usr/bin/perl
use strict; # https://perlmonks.org/?node_id=11118049
use warnings;
use v5.10;
sub add_incr_suffix
{
state $suffix = 'A';
return "prefix-TEXT-" . $suffix++;
}
print 'Test ' .
( add_incr_suffix =~ /^prefix-*/p ? "${^POSTMATCH}" : '' ) . "," .
( add_incr_suffix =~ /^prefix-*/p ? "${^POSTMATCH}" : '' ) . "," .
( add_incr_suffix =~ /^prefix-*/p ? "${^POSTMATCH}" : '' ) . "\n";
Here is a simpler example that produces different output under 5.26 and 5.30
#!/usr/bin/perl
use strict; # https://perlmonks.org/?node_id=11118049
use warnings;
my $foo;
print "test: " . ($foo = 1) . ($foo = 2) . ($foo = 3), "\n";
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|