switch (o->op_type) {
case OP_CONST:
case OP_HINTSEVAL:
- /* with ITHREADS, consts are stored in the pad, and the right pad
+ /* With ITHREADS, consts are stored in the pad, and the right pad
* may not be active here, so check.
- * (((SVOP*)o)->op_sv ? ((SVOP*)o)->op_sv : ((my_perl->Icurpad)[(o)->op_targ]))
+ * Looks like only during compiling the pads are illegal.
*/
- if (((SVOP*)o)->op_sv)
+#ifdef USE_ITHREADS
+ if ((((SVOP*)o)->op_sv) || !IN_PERL_COMPILETIME)
+#endif
PerlIO_printf(Perl_debug_log, "(%s)", SvPEEK(cSVOPo_sv));
break;
case OP_GVSV:
require './test.pl';
}
-use Config;
-
plan tests => 135;
$FS = ':';
is($_ , '1:2:3:4:5:6:::');
# Does assignment to a list imply split to one more field than that?
-SKIP: {
- if ($Config{useithreads}) {
- skip("No IV value dump with threads", 1);
- }
- else {
- $foo = runperl( switches => ['-Dt'], stderr => 1, prog => '($a,$b)=split;' );
- ok($foo =~ /DEBUGGING/ || $foo =~ /const\n?\Q(IV(3))\E/);
- }
-}
+$foo = runperl( switches => ['-Dt'], stderr => 1, prog => '($a,$b)=split;' );
+ok($foo =~ /DEBUGGING/ || $foo =~ /const\n?\Q(IV(3))\E/);
# Can we say how many fields to split to when assigning to a list?
($a,$b) = split(' ','1 2 3 4 5 6', 2);