I recommend that you use the perlbug command line tool to ask p5p to explain the outcome of the following cleaned up version of your program. Include the output.
use strict;
use warnings;
use feature qw( say );
use Data::Dumper qw( Dumper );
BEGIN {
package str;
use strict;
use warnings;
use feature qw( say );
use overload
'""' => \&stringify,
'.' => \&concat;
sub new { my $class = shift; bless([ @_ ], $class) }
sub stringify { join '', @{ $_[0] } }
sub concat {
my ($s1, $s2, $inverted) = @_;
return ref($s1)->new( $inverted ? ($s2,$s1) : ($s1,$s2) );
}
$INC{"str.pm"} = 1;
}
sub _dump {
local $Data::Dumper::Indent = 0;
local $Data::Dumper::Terse = 1;
local $Data::Dumper::Sortkeys = 1;
return Dumper(@_);
}
{
my $str = str->new('foo');
my $good = "a $str a";
say "good: "._dump($good);
my $bad; $bad = "a $str a";
say "bad: "._dump($bad);
}
Output:
good: bless( [bless( ['a ',bless( ['foo'], 'str' )], 'str' ),' a'], 's
+tr' )
bad: 'a foo a'
-
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.