The block that caused the segfault doesn't work the way you think it does, because of precedence:
perl -MO=Deparse -e '
(@n=(1,2) && ($n[1],$n[0]));
(@n=(1,2) && ($n[1],$n[0]));
(@n=(1,2) && ($n[1],$n[0]));
'
@n = ('???', 2) && ($n[1], $n[0]);
@n = ('???', 2) && ($n[1], $n[0]);
@n = ('???', 2) && ($n[1], $n[0]);
Using 'and' instead of && would work, or an extra set of parens.
perl -MO=Deparse -e '
(@n=(1,2) && ($n[1],$n[0]));
((@n=(1,2)) && ($n[1],$n[0]));
(@n=(1,2) and ($n[1],$n[0]));
'
@n = ('???', 2) && ($n[1], $n[0]);
$n[1], $n[0] if @n = (1, 2);
$n[1], $n[0] if @n = (1, 2);
As for the segfault itself, I don't grok why it breaks but Devel::Peek gives a hint:
perl -MDevel::Peek -le '
(@n=(1,2) && ($n[1],$n[0])); print Dump \@n;
(@n=(1,2) && ($n[1],$n[0])); print Dump \@n;'
SV = RV(0x3c02b018) at 0x3c0062dc
REFCNT = 1
FLAGS = (TEMP,ROK)
RV = 0x3c011718
SV = PVAV(0x3c0084dc) at 0x3c011718
REFCNT = 2
FLAGS = ()
IV = 0
NV = 0
ARRAY = 0x3c02a4f0
FILL = 1
MAX = 3
ARYLEN = 0x0
FLAGS = (REAL)
Elt No. 0
SV = NULL(0x0) at 0x3c006168
REFCNT = 1
FLAGS = ()
Elt No. 1
SV = NULL(0x0) at 0x3c006264
REFCNT = 1
FLAGS = ()
SV = RV(0x3c02b018) at 0x3c0062dc
REFCNT = 1
FLAGS = (TEMP,ROK)
RV = 0x3c011718
SV = PVAV(0x3c0084dc) at 0x3c011718
REFCNT = 2
FLAGS = ()
IV = 0
NV = 0
ARRAY = 0x3c02a4f0
FILL = 1
MAX = 3
ARYLEN = 0x0
FLAGS = (REAL)
Elt No. 0
SV = UNKNOWN(0xff) (0x0) at 0x3c006168
REFCNT = 1
FLAGS = ()
Elt No. 1
SV = UNKNOWN(0xff) (0x0) at 0x3c006264
REFCNT = 1
FLAGS = ()
Note that the array entries changed from :
SV = NULL(0x0) at 0x3c006168
To:
SV = UNKNOWN(0xff) (0x0) at 0x3c006168
-
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.